Triple
T26289735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra |
E661233
|
entity |
| Predicate | borderDisputeNature |
P42532
|
FINISHED |
| Object | inter-state boundary dispute |
—
|
LITERAL 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: inter-state boundary dispute | Statement: [Maharashtra, borderDisputeNature, inter-state boundary dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeNature Context triple: [Maharashtra, borderDisputeNature, inter-state boundary dispute]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
C.
frontierDispute
chosen
Indicates a conflict or disagreement between entities over the location, control, or status of a shared boundary or border.
-
D.
hasDisputedMaritimeBoundary
Indicates that there is an unresolved or contested maritime boundary claim between two or more entities.
-
E.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
- 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_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 10:07 p.m.