Triple
T25232289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tughlaq invasion of Warangal |
E632246
|
entity |
| Predicate | commanderForDelhiSultanate |
P159086
|
FINISHED |
| Object | Muhammad bin Tughlaq |
—
|
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: Muhammad bin Tughlaq | Statement: [Tughlaq invasion of Warangal, commanderForDelhiSultanate, Muhammad bin Tughlaq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForDelhiSultanate Context triple: [Tughlaq invasion of Warangal, commanderForDelhiSultanate, Muhammad bin Tughlaq]
-
A.
combatantRulerMughals
Indicates a ruler associated with the Mughal Empire who participated as a combatant in a specific conflict or battle.
-
B.
commanderSeljuk
Indicates that one entity served as a military commander within the Seljuk context (e.g., army, campaign, or polity) for the other entity.
-
C.
commanderForGhaznavids
Indicates that a person served as a military commander on behalf of the Ghaznavid state or dynasty.
-
D.
hasMainCommanderForSikhEmpire
Indicates that one entity serves as the primary military commander for the Sikh Empire.
-
E.
OttomanCommander
Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:06 p.m.