Triple
T17980549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Hills (Tirumala) |
E449589
|
entity |
| Predicate | mythologicalAssociation |
P1481
|
FINISHED |
| Object | Adisesha |
—
|
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: Adisesha | Statement: [Seven Hills (Tirumala), mythologicalAssociation, Adisesha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adisesha Context triple: [Seven Hills (Tirumala), mythologicalAssociation, Adisesha]
-
A.
Sadyojata
Sadyojata is one of the five faces of Lord Shiva, symbolizing creation and the westward aspect of the deity in Shaivite tradition.
-
B.
Anjaneya
Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
-
C.
Samhara-deva
Samhara-deva was a ruler in early medieval India whose throne was seized by the Chaulukya king Mularaja, marking a key dynastic transition in the region.
-
D.
Śeṣa
chosen
Śeṣa is the cosmic serpent and king of all nāgas in Hindu mythology, often depicted as the multi-headed serpent on whom the god Vishnu reclines.
-
E.
Banasura
Banasura is a powerful asura king in Hindu mythology, best known for his thousand arms and his battle with Krishna over his daughter Usha.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b202aab88190b44851808c75a848 |
completed | April 19, 2026, 10:44 a.m. |
Created at: April 10, 2026, 10:22 a.m.