Triple
T36687487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dantidurga |
E905860
|
entity |
| Predicate | predecessorDynastyOverthrown |
P14662
|
FINISHED |
| Object | Badami Chalukya dynasty |
—
|
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: Badami Chalukya dynasty | Statement: [Dantidurga, predecessorDynastyOverthrown, Badami Chalukya dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorDynastyOverthrown Context triple: [Dantidurga, predecessorDynastyOverthrown, Badami Chalukya dynasty]
-
A.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
B.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
C.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
D.
historicalEntityPredecessor
chosen
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
-
E.
predecessorDynasticSituation
Indicates that one dynastic situation directly precedes another in a historical or genealogical sequence.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:12 p.m.