Triple
T9182477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koppal |
E220366
|
entity |
| Predicate | nearbyHeritageSite |
P16759
|
FINISHED |
| Object | Hampi |
E161551
|
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: Hampi | Statement: [Koppal, nearbyHeritageSite, Hampi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hampi Context triple: [Koppal, nearbyHeritageSite, Hampi]
-
A.
Hampi
chosen
Hampi is an ancient ruined city in Karnataka, India, famed for its monumental Hindu temples and as the former capital of the Vijayanagara Empire.
-
B.
Belur
Belur is a locality in the Howrah district of West Bengal, India, known for its proximity to the Hooghly River and the famous Belur Math.
-
C.
Belur
Belur is a historic town in Karnataka, India, renowned for its exquisite Hoysala-era temple architecture, especially the Chennakeshava Temple.
-
D.
Badami
Badami is a historic town in Karnataka, India, renowned for its rock-cut cave temples and ancient Chalukyan architecture.
-
E.
Melkote
Melkote is a historic temple town in Karnataka, India, renowned as a major Vaishnavite pilgrimage center and seat of the Cheluvanarayana Swamy and Yoga Narasimha temples.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc2553e548190898434aeda517407 |
completed | April 1, 2026, 6:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c0eeb0c8190a5a22c662726805c |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:23 p.m.