Triple
T3545422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghiyasuddin Tughlaq |
E74983
|
entity |
| Predicate | roseToPowerAs |
P47710
|
FINISHED |
| Object | military commander under the Khaljis |
—
|
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: military commander under the Khaljis | Statement: [Ghiyasuddin Tughlaq, roseToPowerAs, military commander under the Khaljis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseToPowerAs Context triple: [Ghiyasuddin Tughlaq, roseToPowerAs, military commander under the Khaljis]
-
A.
roseToPowerIn
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
-
B.
methodOfRiseToPower
chosen
Indicates the manner, strategy, or process by which an entity attained power or authority.
-
C.
expandsPowersOf
Indicates that one entity increases, extends, or enhances the authority, capabilities, or influence held by another entity.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
primePowerFormula
Indicates that a value is computed using a formula specifically involving powers of prime numbers.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf77d938819095c72a88b5af644a |
completed | March 8, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.