Triple
T22704200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kollur Mookambika Temple |
E561404
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kollur |
—
|
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: Kollur | Statement: [Kollur Mookambika Temple, locatedIn, Kollur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kollur Context triple: [Kollur Mookambika Temple, locatedIn, Kollur]
-
A.
Kollur
chosen
Kollur is a village in Karnataka, India, best known for the Mookambika Temple, a major Hindu pilgrimage destination.
-
B.
Kollur
Kollur is a rapidly developing suburban area on the outskirts of Hyderabad, Telangana, known for its emerging residential projects and improved connectivity to the city.
-
C.
Gauribidanur
Gauribidanur is a town in the Indian state of Karnataka known for its educational institutions, nearby research facilities, and role as a local commercial center.
-
D.
Gorikot
Gorikot is a village and local hub in Pakistan’s Astore Valley, serving as a gateway to nearby mountain regions and trekking routes.
-
E.
Devanahalli
Devanahalli is a town near Bengaluru in the Indian state of Karnataka, notable for its rapid development and proximity to Kempegowda International Airport.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cca1e48190bbe7910f13692803 |
completed | April 29, 2026, 3:19 a.m. |
Created at: April 17, 2026, 3:16 p.m.