Triple
T28173254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milan–Chiasso railway |
E715518
|
entity |
| Predicate | crossBorderSection |
P173239
|
FINISHED |
| Object | Chiasso–Como segment |
—
|
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: Chiasso–Como segment | Statement: [Milan–Chiasso railway, crossBorderSection, Chiasso–Como segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderSection Context triple: [Milan–Chiasso railway, crossBorderSection, Chiasso–Como segment]
-
A.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
B.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
C.
crossBorderGatewayFor
Indicates that one entity functions as a gateway enabling traffic or interaction to cross a border or boundary for another entity.
-
D.
crossBorderNode
Indicates a connection or element that spans or links entities across a defined boundary or border.
-
E.
crossedBoundary
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 10:14 p.m.