Triple
T33867095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripura Sundari |
E868087
|
entity |
| Predicate | positionInMahavidyas |
P143594
|
FINISHED |
| Object | third Mahavidya |
—
|
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: third Mahavidya | Statement: [Tripura Sundari, positionInMahavidyas, third Mahavidya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMahavidyas Context triple: [Tripura Sundari, positionInMahavidyas, third Mahavidya]
-
A.
positionInSriYantra
Indicates the specific spatial location or role that an element occupies within the geometric structure of the Sri Yantra.
-
B.
numberInMahavidyas
chosen
Indicates the specific ordinal position or count assigned to an entity within the set of Mahavidyas.
-
C.
positionInNavagraha
Indicates the specific ordinal place an entity occupies within the ordered set of the nine Navagraha celestial bodies.
-
D.
positionInTheology
Indicates the role, stance, or status that something or someone holds within a particular theological framework or system.
-
E.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 1, 2026, 1:47 a.m.