Triple
T13479874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Dinajara |
E318343
|
entity |
| Predicate | successorDynastyOrigin |
P110551
|
FINISHED |
| Object | South Indian |
—
|
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: South Indian | Statement: [House of Dinajara, successorDynastyOrigin, South Indian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyOrigin Context triple: [House of Dinajara, successorDynastyOrigin, South Indian]
-
A.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
C.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
D.
successorDynasticPhase
Indicates that one dynastic phase directly follows and replaces another in a historical or genealogical sequence.
-
E.
dynastyFoundedByOffspring
Indicates that a dynasty was established by the offspring (child or descendant) of a particular person or entity.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf36c6b08190ba99400600e0b662 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:42 p.m.