Triple
T36160572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domodossola railway station |
E1045862
|
entity |
| Predicate | railwayBorderCrossingWith |
P182398
|
FINISHED |
| Object | Switzerland |
—
|
NE NERFINISHED |
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: Switzerland | Statement: [Domodossola railway station, railwayBorderCrossingWith, Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayBorderCrossingWith Context triple: [Domodossola railway station, railwayBorderCrossingWith, Switzerland]
-
A.
hasRailBorderCrossing
Indicates that two places are connected by at least one official border crossing that is served by rail transport.
-
B.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
C.
hasBorderRailConnectionWith
chosen
Indicates that two places are directly connected to each other by a cross-border railway line or service.
-
D.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
E.
connectsToBorderPost
Indicates that one entity is linked or leads directly to a border post, establishing a route or connection between them.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.