Triple
T24030556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toghrul |
E595091
|
entity |
| Predicate | relativeByAlliance |
P154577
|
FINISHED |
| Object | Yesugei |
—
|
NE NERFINISHED |
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: Yesugei | Statement: [Toghrul, relativeByAlliance, Yesugei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeByAlliance Context triple: [Toghrul, relativeByAlliance, Yesugei]
-
A.
allianceOrRivalry
Indicates a relationship where entities are either cooperating as allies or competing as rivals, capturing both partnership and opposition dynamics.
-
B.
relationshipToAlly
Indicates the type or nature of a subject's connection or association with an ally.
-
C.
involvesAlliance
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
D.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
E.
vassalOrAllyOf
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
- F. None of above. chosen
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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76fbedc8190a2f936729cb69993 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 9:55 p.m.