Triple
T17939897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirumala Hills |
E448558
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Balaji |
—
|
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: Balaji | Statement: [Tirumala Hills, hasDeity, Balaji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Balaji Context triple: [Tirumala Hills, hasDeity, Balaji]
-
A.
Balaji
chosen
Balaji is a common Indian given name, often associated with Hindu tradition and notably borne by historical figures such as Balaji Vishwanath, the first Peshwa of the Maratha Empire.
-
B.
Salasar Balaji
Salasar Balaji is a renowned Hindu pilgrimage site in Rajasthan, India, famous for its temple dedicated to Lord Hanuman.
-
C.
Kailasam
Kailasam is the given name of renowned Indian filmmaker and playwright K. Balachander, a major figure in Tamil cinema and theatre.
-
D.
Chakrapani
Chakrapani is a Hindu deity, regarded as a form of Lord Vishnu associated with the discus (chakra) and worshipped as the presiding god of the Chakrapani Temple.
-
E.
Brihadbala
Brihadbala was a king of Kosala and a warrior in the Mahabharata epic, known for fighting on the Kaurava side in the Kurukshetra War.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 10:21 a.m.