Triple
T3254409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lodi dynasty |
E68260
|
entity |
| Predicate | dynastyType |
P14587
|
FINISHED |
| Object | Turko-Afghan sultanate dynasty |
—
|
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: Turko-Afghan sultanate dynasty | Statement: [Lodi dynasty, dynastyType, Turko-Afghan sultanate dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyType Context triple: [Lodi dynasty, dynastyType, Turko-Afghan sultanate dynasty]
-
A.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
B.
dynasticType
chosen
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
C.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
D.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
E.
dynasticContext
Indicates the historical or political circumstances defined by a particular ruling dynasty under which the related entities or events are situated.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf65c9388190a0d74d6365ce631e |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.