Triple
T10986511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thousand Pillar Temple |
E259643
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Hanamakonda |
E897715
|
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: Hanamakonda | Statement: [Thousand Pillar Temple, locatedIn, Hanamakonda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanamakonda Context triple: [Thousand Pillar Temple, locatedIn, Hanamakonda]
-
A.
Hanamkonda
chosen
Hanamkonda is a major urban area and historical locality in the Indian state of Telangana, forming part of the tri-city region along with Warangal and Kazipet.
-
B.
Narayanavanam
Narayanavanam is a small town in the Tirupati district of Andhra Pradesh, India, known for its historic temples and religious significance.
-
C.
Allagadda
Allagadda is a town and legislative assembly constituency in the Nandyal district of Andhra Pradesh, India.
-
D.
Tadipatri
Tadipatri is a town in the Anantapur district of Andhra Pradesh, India, known for its granite industries and historic temples.
-
E.
Mokshagundam
Mokshagundam is the given name of Sir M. Visvesvaraya, a renowned Indian engineer, statesman, and Bharat Ratna awardee.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b2e4a88190a81504eee77e2298 |
completed | April 9, 2026, 11:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e717481c81908800cd785537c8fc |
completed | April 18, 2026, 8:18 p.m. |
Created at: April 8, 2026, 9:24 p.m.