Triple
T21820693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ātman |
E538716
|
entity |
| Predicate | realizationLeadsTo |
P18658
|
FINISHED |
| Object | mokṣa |
—
|
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: mokṣa | Statement: [Ātman, realizationLeadsTo, mokṣa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realizationLeadsTo Context triple: [Ātman, realizationLeadsTo, mokṣa]
-
A.
hasRealizationAs
Indicates that something abstract, such as a plan, design, or concept, is concretely implemented or manifested as a particular realized form.
-
B.
goalOfRealization
Indicates the intended outcome or objective that an action, process, or plan is meant to bring into reality or achieve.
-
C.
canLeadTo
chosen
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
-
D.
realizationMethod
Indicates the means, process, or technique by which something is carried out, implemented, or brought into effect.
-
E.
finalRealization
Indicates the culminating recognition or understanding that occurs at the end of a process, event, or sequence of actions.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0912d414c81909c109c3e45b6e7d2 |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.