Triple
T990479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbo, Colombia |
E21376
|
entity |
| Predicate | isPointWhere |
P22813
|
FINISHED |
| Object | Pan-American Highway is discontinuous |
—
|
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: Pan-American Highway is discontinuous | Statement: [Turbo, Colombia, isPointWhere, Pan-American Highway is discontinuous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPointWhere Context triple: [Turbo, Colombia, isPointWhere, Pan-American Highway is discontinuous]
-
A.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
B.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
C.
containsPoint
Indicates that a geometric region or shape includes a given point within its boundaries.
-
D.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
E.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
- F. None of above. chosen
Provenance (4 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4ac27e081908f132115464667b2 |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2adbde48190b07966d0c3179516 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.