Triple
T26289724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra |
E661233
|
entity |
| Predicate | borderDisputeKeyCity |
P49394
|
FINISHED |
| Object | Belagavi |
—
|
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: Belagavi | Statement: [Maharashtra, borderDisputeKeyCity, Belagavi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeKeyCity Context triple: [Maharashtra, borderDisputeKeyCity, Belagavi]
-
A.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
B.
borderDisputesWith
chosen
Indicates that there are contested or unresolved boundary claims between two entities.
-
C.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
D.
borderCityStatus
Indicates that a city holds a designated status due to its location on or near a political or geographic border.
-
E.
borderSettlement
Indicates that a settlement is located near or along a political or administrative border.
- F. None of above.
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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 26, 2026, 10:07 p.m.