Triple
T29581347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecuadorian–Peruvian territorial disputes |
E753594
|
entity |
| Predicate | involvesBorder |
P43209
|
FINISHED |
| Object | Ecuador–Peru border |
—
|
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: Ecuador–Peru border | Statement: [Ecuadorian–Peruvian territorial disputes, involvesBorder, Ecuador–Peru border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesBorder Context triple: [Ecuadorian–Peruvian territorial disputes, involvesBorder, Ecuador–Peru border]
-
A.
relatedBorder
chosen
Indicates that two geographic or political entities share a common boundary or border with each other.
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
languageBorderInvolved
Indicates that a situation, event, or relationship involves or is affected by a boundary between different languages or linguistic communities.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
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_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:07 p.m.