Triple
T17803144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasir-ud-Din Mahmud Shah Tughlaq |
E444484
|
entity |
| Predicate | associatedDynastyEnd |
P59019
|
FINISHED |
| Object | fall of Tughlaq dynasty in 1413 |
—
|
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: fall of Tughlaq dynasty in 1413 | Statement: [Nasir-ud-Din Mahmud Shah Tughlaq, associatedDynastyEnd, fall of Tughlaq dynasty in 1413]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynastyEnd Context triple: [Nasir-ud-Din Mahmud Shah Tughlaq, associatedDynastyEnd, fall of Tughlaq dynasty in 1413]
-
A.
dynastyEndedWith
chosen
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
B.
hasLastDynasty
Indicates that an entity’s most recent or final ruling dynasty is the specified dynasty.
-
C.
lastReigningDynastyOf
Indicates that one dynasty is the final ruling dynasty to have governed a particular political entity or territory.
-
D.
extinctDynasty
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
-
E.
dynastyDissolutionCause
Indicates the reason or factor that led to the dissolution or end of a dynasty.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880171608190be2088c7a387bfb7 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.