Triple
T3311490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hülegü Khan |
E69581
|
entity |
| Predicate | aftermathOfRule |
P46175
|
FINISHED |
| Object | consolidation of Mongol rule in Iran |
—
|
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: consolidation of Mongol rule in Iran | Statement: [Hülegü Khan, aftermathOfRule, consolidation of Mongol rule in Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftermathOfRule Context triple: [Hülegü Khan, aftermathOfRule, consolidation of Mongol rule in Iran]
-
A.
aftermathPolicy
Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
-
B.
handledAftermathOf
Indicates that one entity took responsibility for dealing with the consequences or fallout that occurred after another entity’s actions or events.
-
C.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
afterConquest
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
E.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0ec80508190baa78435b983b7b5 |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.