Triple
T19026401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diti |
E465620
|
entity |
| Predicate | parent |
P120
|
FINISHED |
| Object | Daksha |
—
|
NE NERFINISHED |
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: Daksha | Statement: [Diti, parent, Daksha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daksha Context triple: [Diti, parent, Daksha]
-
A.
Daksha
Daksha was a ruler who succeeded King Balitung in the line of Mataram (Medang) monarchs in early medieval Java.
-
B.
Daksha
chosen
Daksha is a prominent Vedic deity and progenitor figure in Hindu mythology, often associated with creation, ritual order, and the lineage of gods and sages.
-
C.
Purushottama Deva
Purushottama Deva was a prominent 15th-century king of Odisha known for expanding the Gajapati Empire and patronizing the Jagannath cult and temple architecture.
-
D.
Vrushabhadri
Vrushabhadri is one of the sacred hills of the Tirumala range associated with the Tirumala Venkateswara Temple in Andhra Pradesh, India.
-
E.
Mahadeva
Mahadeva is a principal form of the Hindu god Shiva, revered as the supreme deity and great lord in Shaivism.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d73cace0819096bdac6dc8c17253 |
completed | April 20, 2026, 7:35 a.m. |
Created at: April 10, 2026, 12:02 p.m.