Triple
T6044500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kena Upanishad |
E134631
|
entity |
| Predicate | positionInMukhyaUpanishads |
P68375
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Kena Upanishad, positionInMukhyaUpanishads, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMukhyaUpanishads Context triple: [Kena Upanishad, positionInMukhyaUpanishads, 4]
-
A.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
B.
associatedUpanishad
Indicates a relationship where something is linked or connected to a particular Upanishad as its source, reference, or context.
-
C.
viewOnVedas
Indicates the stance, opinion, or interpretive perspective that one entity holds regarding the Vedas.
-
D.
hasPositionInMahabharata
Indicates that one entity holds or is assigned a specific role, rank, or position within the context of the Mahabharata narrative.
-
E.
positionInMishnahOrders
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e2b1148190908c4dc43abee266 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:09 p.m.