Triple
T5060979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yudhishthira |
E114019
|
entity |
| Predicate | ascendedTo |
P61030
|
FINISHED |
| Object | heaven in his mortal body |
—
|
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: heaven in his mortal body | Statement: [Yudhishthira, ascendedTo, heaven in his mortal body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendedTo Context triple: [Yudhishthira, ascendedTo, heaven in his mortal body]
-
A.
ascensionMethod
Indicates the means or process by which an entity rises, advances, or transitions to a higher state, level, or position.
-
B.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
C.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
D.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
-
E.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74740ae08190930f1fd57187334e |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:38 p.m.