Triple
T24378981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajadhiraja I |
E614556
|
entity |
| Predicate | successorAsCoRegent |
P155982
|
FINISHED |
| Object | Rajendra 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: Rajendra II | Statement: [Rajadhiraja I, successorAsCoRegent, Rajendra II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsCoRegent Context triple: [Rajadhiraja I, successorAsCoRegent, Rajendra II]
-
A.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
B.
successorAsCoRulerOf
Indicates that one entity became the next co-ruler alongside another entity, following a previous co-ruler in a shared rulership position.
-
C.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
-
D.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
E.
successorAsCrownPrince
Indicates that one person becomes the next crown prince, directly succeeding another in that royal position.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293da489c81909a7912b790be8b8a |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:02 a.m.