Triple
T19127410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yajna Sri Satakarni |
E468220
|
entity |
| Predicate | associatedDynasticPhase |
P7426
|
FINISHED |
| Object | late Satavahana period |
—
|
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: late Satavahana period | Statement: [Yajna Sri Satakarni, associatedDynasticPhase, late Satavahana period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynasticPhase Context triple: [Yajna Sri Satakarni, associatedDynasticPhase, late Satavahana period]
-
A.
successorDynasticPhase
Indicates that one dynastic phase directly follows and replaces another in a historical or genealogical sequence.
-
B.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
C.
associatedWithDynasty
chosen
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
D.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cd851081909d5665b362ae08de |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.