Triple
T38585952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durak |
E932345
|
entity |
| Predicate | notableParentRole |
P123178
|
FINISHED |
| Object | former Warchief of the Horde |
—
|
LITERAL 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: former Warchief of the Horde | Statement: [Durak, notableParentRole, former Warchief of the Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableParentRole Context triple: [Durak, notableParentRole, former Warchief of the Horde]
-
A.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
B.
notableRecipientRole
Indicates that an entity has received a notable award, honor, or recognition specifically in the capacity of a particular role or position.
-
C.
notableRelativeType
chosen
Indicates the specific familial or relational role that a notable relative has in relation to the subject.
-
D.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
E.
notableBearerOfRole
Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
- F. None of above.
Provenance (3 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.