Triple
T36687558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishna I |
E905861
|
entity |
| Predicate | successorAsRuler |
P45012
|
FINISHED |
| Object | Govinda II |
—
|
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: Govinda II | Statement: [Krishna I, successorAsRuler, Govinda II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsRuler Context triple: [Krishna I, successorAsRuler, Govinda II]
-
A.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
B.
successorRuler
chosen
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
C.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
D.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
E.
successorAsCoRegent
Indicates that one entity becomes the next co-ruling authority alongside an existing ruler, succeeding another in the role of co-regent.
- 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_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: May 3, 2026, 4:12 p.m.