Triple
T32479312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punto Concordia (disputed designation) |
E830064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | border endpoint |
C56000
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: border endpoint Context triple: [Punto Concordia (disputed designation), instanceOf, border endpoint]
-
A.
border junction
chosen
A border junction is a point or area where the boundaries of two or more distinct regions, territories, or systems meet and interact.
-
B.
border corridor
A border corridor is a designated strip of land or airspace that provides controlled access or transit along or across a political boundary between two or more territories.
-
C.
border city
A border city is an urban settlement located near or directly on the boundary between two or more political or geographic regions, serving as a hub for cross-border movement, trade, and cultural exchange.
-
D.
border town
A border town is a settlement located near or directly on the boundary between two political or geographic regions, often serving as a hub for trade, transit, and cultural exchange.
-
E.
border territory
A border territory is a geographic area situated along the boundary between two or more political entities, often characterized by heightened strategic, cultural, and economic significance.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 12:58 a.m.