Triple
T26289709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra |
E661233
|
entity |
| Predicate | borderDisputeFocusRegion |
P62086
|
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, borderDisputeFocusRegion, Belagavi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeFocusRegion Context triple: [Maharashtra, borderDisputeFocusRegion, Belagavi]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
C.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
D.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
E.
boundaryReviewRegion
chosen
Indicates that a specified region is under consideration or subject to evaluation in a boundary review process.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 26, 2026, 10:07 p.m.