Triple
T21897240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nachiketa |
E540711
|
entity |
| Predicate | seeksFromYama |
P146094
|
FINISHED |
| Object | knowledge of what happens after death |
—
|
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: knowledge of what happens after death | Statement: [Nachiketa, seeksFromYama, knowledge of what happens after death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksFromYama Context triple: [Nachiketa, seeksFromYama, knowledge of what happens after death]
-
A.
seeksFromIvanIlyich
Indicates that an entity actively seeks or requests something from Ivan Ilyich.
-
B.
yaksha
Indicates a relationship or action involving a yaksha, typically denoting interaction with, influence by, or association to this mythological being.
-
C.
hasOmamori
Indicates that one entity possesses or is associated with an omamori (a protective charm or amulet).
-
D.
YamayakiIncludes
Indicates that something is part of, or contained within, the Yamayaki event or process.
-
E.
Seal of the Hands
Indicates a relationship in which something is formally confirmed, authenticated, or bound through the deliberate action or agreement of specific individuals or parties.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc7c70c81908b9bb4de68616e41 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:07 p.m.