Triple
T559092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich |
E13407
|
entity |
| Predicate | railwayStationRole |
P5885
|
FINISHED |
| Object | major railway hub in Switzerland |
—
|
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: major railway hub in Switzerland | Statement: [Zurich, railwayStationRole, major railway hub in Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStationRole Context triple: [Zurich, railwayStationRole, major railway hub in Switzerland]
-
A.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
B.
railNetworkRole
chosen
Indicates the specific function or responsibility an entity has within a rail network system.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
E.
railwayJunctionFor
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499df43f08190b514a38d36fc271d |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494bd78e8819083c519669158f209 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.