Triple
T27920646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardo Thodol |
E706193
|
entity |
| Predicate | hasNotableTranslator |
P153486
|
FINISHED |
| Object | Walter Evans-Wentz |
—
|
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: Walter Evans-Wentz | Statement: [Bardo Thodol, hasNotableTranslator, Walter Evans-Wentz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTranslator Context triple: [Bardo Thodol, hasNotableTranslator, Walter Evans-Wentz]
-
A.
notableEnglishTranslator
Indicates that one entity is a notable translator who has translated works into English or is recognized for English translation.
-
B.
hasWorkTranslatedBy
chosen
Indicates that a work has been rendered into another language or form by a specific translator.
-
C.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
D.
hasWorkTranslatedInto
Indicates that a work has been translated into a specified language or target work.
-
E.
hasInfluentialTranslation
Indicates that an entity has a translation which has significantly shaped, spread, or impacted the understanding or reception of the original work.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: April 27, 2026, 6:56 p.m.