Triple
T5906367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vayu Purana |
E131349
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Vayu |
E117377
|
NE 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: Vayu | Statement: [Vayu Purana, namedAfter, Vayu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vayu Context triple: [Vayu Purana, namedAfter, Vayu]
-
A.
Vayu
chosen
Vayu is the Hindu god of wind, revered as a powerful Vedic deity and divine father of the monkey-god Hanuman.
-
B.
Vinata
Vinata is a figure in Hindu mythology known as the mother of Garuda and a consort of the sage Kashyapa.
-
C.
Devaka
Devaka is a figure in Hindu tradition known primarily as the father of Devaki, the mother of the deity Krishna.
-
D.
Vaisesika
Vaisesika is one of the six classical schools of Indian philosophy, known for its atomistic metaphysics and detailed categorization of reality.
-
E.
Vrishni
Vrishni was a prominent clan within the ancient Yadava lineage of India, traditionally associated with Lord Krishna and centered around the region of Mathura and Dvaraka.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0377159f88190a142cd7eed6118c1 |
completed | March 22, 2026, 6:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b16ba6c881908e9a909bf86ea92d |
completed | March 23, 2026, 3:20 a.m. |
Created at: March 22, 2026, 3:59 p.m.