Triple
T32621991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avaroa–Ollagüe rail crossing |
E833950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway border point |
C43963
|
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: railway border point Context triple: [Avaroa–Ollagüe rail crossing, instanceOf, railway border point]
-
A.
rail border crossing
chosen
A rail border crossing is a designated point where railway lines intersect an international boundary, enabling the controlled movement of trains, cargo, and passengers between countries.
-
B.
road–rail border crossing
A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
-
C.
international border point
An international border point is a designated location where people, goods, and vehicles legally cross from one country into another under the control of official authorities.
-
D.
railway junction
A railway junction is a point on a rail network where two or more railway lines meet or diverge, allowing trains to switch between different routes.
-
E.
railway portal
A railway portal is a structural entrance or gateway, typically at the mouth of a tunnel or major rail facility, that marks the transition between open track and enclosed or specialized railway infrastructure.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:06 a.m.