Triple
T18725210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Canara |
E457881
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Kumta |
—
|
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: Kumta | Statement: [North Canara, hasTown, Kumta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kumta Context triple: [North Canara, hasTown, Kumta]
-
A.
Kumta
chosen
Kumta is a coastal town in Karnataka, India, known for its beaches, temples, and proximity to the Western Ghats.
-
B.
Kumher
Kumher is a historic town in the Braj region of northern India, known for its cultural and religious significance linked to the legends of Lord Krishna.
-
C.
Khadakwasla
Khadakwasla is a suburban area near Pune in Maharashtra, India, known for its lake, dam, and military establishments.
-
D.
Khambha
Khambha is a town in the Amreli district of Gujarat, India, known primarily as a local commercial and agricultural center.
-
E.
Chakdara
Chakdara is a town in Pakistan’s Khyber Pakhtunkhwa province, known as a strategic gateway to the Swat Valley and an area rich in archaeological and historical significance.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d72d2c4819080b0d31860976b5e |
completed | April 20, 2026, 12:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.