Triple
T26926095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malavikagnimitram |
E677781
|
entity |
| Predicate | protagonistDynasty |
P161988
|
FINISHED |
| Object | Shunga 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: Shunga dynasty | Statement: [Malavikagnimitram, protagonistDynasty, Shunga dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistDynasty Context triple: [Malavikagnimitram, protagonistDynasty, Shunga dynasty]
-
A.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
B.
creatorDynasty
Indicates the historical dynasty or ruling period during which the creator of an entity lived or was active.
-
C.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
D.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
E.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 6:09 a.m.