Triple
T36301006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiasso railway station |
E893511
|
entity |
| Predicate | locatedNearBorderCrossing |
P27684
|
FINISHED |
| Object | Chiasso–Como road border |
E1488562
|
NE 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: Chiasso–Como road border | Statement: [Chiasso railway station, locatedNearBorderCrossing, Chiasso–Como road border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearBorderCrossing Context triple: [Chiasso railway station, locatedNearBorderCrossing, Chiasso–Como road border]
-
A.
nearBorderCrossing
chosen
Indicates that an entity is located close to a border crossing point between two regions or countries.
-
B.
hasNearbyCrossBorderInfrastructure
Indicates that there exists infrastructure located near a border that connects or serves entities on both sides of that border.
-
C.
hasNearbySettlementAcrossBorder
Indicates that one settlement is located close to another settlement that lies just across an intervening political or administrative border.
-
D.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
E.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
- F. None of above.
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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d802d948190b95f4d1aff327290 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.