Triple
T13223269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kankavli taluka |
E314808
|
entity |
| Predicate | administrativeCentre |
P1474
|
FINISHED |
| Object | Kankavli |
E314804
|
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: Kankavli | Statement: [Kankavli taluka, administrativeCentre, Kankavli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kankavli Context triple: [Kankavli taluka, administrativeCentre, Kankavli]
-
A.
Kankavli
chosen
Kankavli is a prominent town in Maharashtra’s Sindhudurg district, known as a key commercial and transport hub in the Konkan region.
-
B.
Malavalli
Malavalli is a town in the Mandya district of Karnataka, India, known for its proximity to the Shimsha River and its agricultural surroundings.
-
C.
Pindiali
Pindiali is a settlement located in the Mohmand region of northwestern Pakistan, near the border with Afghanistan.
-
D.
Vengurla
Vengurla is a coastal town in Maharashtra, India, known for its scenic beaches, historic forts, and cashew plantations.
-
E.
Nalut
Nalut is a town in western Libya situated in the Nafusa Mountains, known for its Amazigh (Berber) heritage and historic hilltop granaries.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf74d708190a61d8ad938653b06 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff24be9881908b96f3e72325e55f |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:19 p.m.