Triple
T10736683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kundapura taluk |
E253212
|
entity |
| Predicate | administrativeCentre |
P1474
|
FINISHED |
| Object | Kundapura |
E262300
|
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: Kundapura | Statement: [Kundapura taluk, administrativeCentre, Kundapura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kundapura Context triple: [Kundapura taluk, administrativeCentre, Kundapura]
-
A.
Kundapura
chosen
Kundapura is a coastal town in the Udupi district of Karnataka, India, known for its temples, beaches, and distinct regional culture.
-
B.
Bhatkal
Bhatkal is a historic coastal town in Karnataka, India, known for its Arabian Sea shoreline, trading legacy, and distinctive Nawayath Muslim culture.
-
C.
Gorikot
Gorikot is a village and local hub in Pakistan’s Astore Valley, serving as a gateway to nearby mountain regions and trekking routes.
-
D.
Battakundi
Battakundi is a small scenic village and tourist stopover located in Pakistan’s mountainous Kaghan Valley.
-
E.
Karanpur
Karanpur is a town located in the Ganganagar district of the northern Indian state of Rajasthan.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71022aee0819091a5790d3dee6777 |
completed | April 9, 2026, 2:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2162f1f648190b325c7e7647b543e |
completed | April 17, 2026, 11:14 a.m. |
Created at: April 8, 2026, 9:14 p.m.