Triple
T38022596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Rastakhan |
E948680
|
entity |
| Predicate | notableLoaPact |
P22580
|
FINISHED |
| Object | Bwonsamdi |
E933336
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Bwonsamdi | Statement: [King Rastakhan, notableLoaPact, Bwonsamdi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLoaPact Context triple: [King Rastakhan, notableLoaPact, Bwonsamdi]
-
A.
notableAccord
Indicates a significant formal agreement, treaty, or understanding established between entities.
-
B.
notableAllegiance
chosen
Indicates a significant or historically important loyalty or affiliation that one entity has toward another, such as a person’s primary side, cause, or organization they are known for supporting.
-
C.
notableContract
Indicates that there exists a contract or agreement between entities that is of particular significance, prominence, or public interest.
-
D.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
-
E.
notableArc
Indicates a significant or defining narrative development, transformation, or storyline involving the related entities.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d2aa4448190a9ae7a6ff99985c6 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.