Triple
T6194812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praśna Upanishad |
E138482
|
entity |
| Predicate | fifthQuestionTopic |
P69592
|
FINISHED |
| Object | meditation on Om and its results |
—
|
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: meditation on Om and its results | Statement: [Praśna Upanishad, fifthQuestionTopic, meditation on Om and its results]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifthQuestionTopic Context triple: [Praśna Upanishad, fifthQuestionTopic, meditation on Om and its results]
-
A.
fifthWork
Indicates that one entity is the fifth work (e.g., in a series, catalog, or sequence) associated with another entity.
-
B.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
C.
questionFormulation
Indicates that one entity formulates, poses, or expresses a question directed toward another entity or context.
-
D.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
-
E.
fifthMysteryName
Indicates that an entity is identified by the name or title of the fifth mystery in a specific ordered set of mysteries.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062443cec81909dc9bafea2f5e7d4 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:19 p.m.