Triple
T20182199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharmaputra |
E492755
|
entity |
| Predicate | onlyPandavaToReachHeavenInBody |
P28307
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dharmaputra, onlyPandavaToReachHeavenInBody, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlyPandavaToReachHeavenInBody Context triple: [Dharmaputra, onlyPandavaToReachHeavenInBody, true]
-
A.
hasBodhisattva
Indicates that one entity includes, is associated with, or is characterized by the presence or guidance of a bodhisattva.
-
B.
takenUpToHeaven
chosen
Indicates that an entity has been carried or ascended from an earthly or mortal realm into a heavenly or divine realm.
-
C.
isPandavaSon
Indicates that one entity is the son of a member of the Pandava brothers.
-
D.
involvesChineseBody
Indicates that the situation, event, or context includes participation or presence of a Chinese organization, institution, or official body.
-
E.
Xiaoerjing
Indicates a relationship where something is written, represented, or transcribed using the Xiaoerjing (Arabic-based) script for Sinitic languages.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ef9370819091a8479f811002a9 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.