Triple
T4823585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karna |
E107766
|
entity |
| Predicate | boonFrom |
P29971
|
FINISHED |
| Object | Indra |
E102073
|
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: Indra | Statement: [Karna, boonFrom, Indra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Indra Context triple: [Karna, boonFrom, Indra]
-
A.
Indra
chosen
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
-
B.
Vivasvan
Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
-
C.
Dyaus Pitar
Dyaus Pitar is the ancient Vedic sky god, regarded as a primordial father figure and etymological cognate of the Greek Zeus and Roman Jupiter.
-
D.
Vishrava
Vishrava is a revered sage in Hindu mythology, best known as the father of the demon king Ravana and his giant brother Kumbhakarna in the Ramayana.
-
E.
Vrushabhadri
Vrushabhadri is one of the sacred hills of the Tirumala range associated with the Tirumala Venkateswara Temple in Andhra Pradesh, India.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6cac2bd08190b3f7cfe691fed052 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be778a642081908761067765ba09c8 |
completed | March 21, 2026, 10:48 a.m. |
Created at: March 20, 2026, 1:24 p.m.