Triple
T29575557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limpiyadhura area |
E753433
|
entity |
| Predicate | hasBorderDisputeBetween |
P49394
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [Limpiyadhura area, hasBorderDisputeBetween, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderDisputeBetween Context triple: [Limpiyadhura area, hasBorderDisputeBetween, India]
-
A.
borderDisputesWith
chosen
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
hasDisputedMaritimeBoundary
Indicates that there is an unresolved or contested maritime boundary claim between two or more entities.
-
C.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
D.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
-
E.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 6:02 p.m.