Triple
T5932797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Karnataka |
E131975
|
entity |
| Predicate | majorTown |
P316
|
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: [Coastal Karnataka, majorTown, Kundapura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kundapura Context triple: [Coastal Karnataka, majorTown, 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.
Gorikot
Gorikot is a village and local hub in Pakistan’s Astore Valley, serving as a gateway to nearby mountain regions and trekking routes.
-
C.
Battakundi
Battakundi is a small scenic village and tourist stopover located in Pakistan’s mountainous Kaghan Valley.
-
D.
Kushalnagar
Kushalnagar is a town in Karnataka’s Kodagu district, known as a gateway to the Coorg region and nearby river, dam, and nature attractions.
-
E.
Kabini
Kabini is a river and popular wildlife and tourism region in southern India, known for its reservoir, lush forests, and rich biodiversity.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0389df18c81909027a9db7596f0c1 |
completed | March 22, 2026, 6:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0c064d2a4819096085668182cfde1 |
completed | March 23, 2026, 4:24 a.m. |
Created at: March 22, 2026, 4 p.m.