Triple
T32479320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punto Concordia (disputed designation) |
E830064
|
entity |
| Predicate | borderEndpointOf |
P43807
|
FINISHED |
| Object | land boundary between Peru and Chile |
—
|
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: land boundary between Peru and Chile | Statement: [Punto Concordia (disputed designation), borderEndpointOf, land boundary between Peru and Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderEndpointOf Context triple: [Punto Concordia (disputed designation), borderEndpointOf, land boundary between Peru and Chile]
-
A.
borderPoint
chosen
Indicates a point that lies on the boundary between two regions or entities.
-
B.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
C.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
D.
borderTypeAtTerminusB
Indicates the type or classification of the border present at the second (B) endpoint of a defined boundary or connection.
-
E.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 1, 2026, 12:58 a.m.