Triple
T29732494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simhavishnu |
E752366
|
entity |
| Predicate | successorDynast |
P45012
|
FINISHED |
| Object | Mahendravarman I |
—
|
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: Mahendravarman I | Statement: [Simhavishnu, successorDynast, Mahendravarman I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynast Context triple: [Simhavishnu, successorDynast, Mahendravarman I]
-
A.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
C.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
D.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
E.
successorRuler
chosen
Indicates that one ruler directly follows another in holding a position of authority or rule.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 28, 2026, 7:43 p.m.