Triple
T23562805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnimitra |
E579286
|
entity |
| Predicate | chronologicalOrderInDynasty |
P54591
|
FINISHED |
| Object | second Shunga king |
—
|
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: second Shunga king | Statement: [Agnimitra, chronologicalOrderInDynasty, second Shunga king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderInDynasty Context triple: [Agnimitra, chronologicalOrderInDynasty, second Shunga king]
-
A.
dynasticOrder
chosen
Indicates the hierarchical sequence of rulers or family lines within a dynasty, specifying who precedes or follows whom in dynastic succession.
-
B.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
C.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
D.
hasDynasticOrder
Indicates that there exists a specific sequence or hierarchy of dynasties or ruling lines associated with the subject.
-
E.
chronologicalOrderInSuccessionWar
Indicates the temporal sequence in which entities participate or occur within the context of the Succession War.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6a02208190b7d35c4e5da67a44 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:25 p.m.