Triple
T5614515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cenepa War |
E147442
|
entity |
| Predicate | statusOfBorderAfterConflict |
P4701
|
FINISHED |
| Object | border fully demarcated by 1998 |
—
|
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: border fully demarcated by 1998 | Statement: [Cenepa War, statusOfBorderAfterConflict, border fully demarcated by 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfBorderAfterConflict Context triple: [Cenepa War, statusOfBorderAfterConflict, border fully demarcated by 1998]
-
A.
demilitarizedBorderWith
Indicates that a border between two entities exists where military forces, installations, and activities are restricted or prohibited by agreement.
-
B.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
C.
legalStatusAfterWar
chosen
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
D.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02123fa9081909086c9cce3f3e907 |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.