Triple
T4515575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandavas |
E102144
|
entity |
| Predicate | succeedTo |
P43223
|
FINISHED |
| Object | throne of Hastinapura |
—
|
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: throne of Hastinapura | Statement: [Pandavas, succeedTo, throne of Hastinapura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeedTo Context triple: [Pandavas, succeedTo, throne of Hastinapura]
-
A.
succeedsTo
chosen
Indicates that one entity takes over a role, position, or function previously held by another entity, following it in sequence or authority.
-
B.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
-
C.
succeedsFrom
Indicates that one entity comes after, replaces, or follows another in a sequence, order, or succession.
-
D.
succeededByName
Indicates that one entity is followed or replaced by another entity identified by a specific name.
-
E.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5725745c81908bb462ba9537ae14 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.