Triple
T20484684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-Bahn Luzern |
E502556
|
entity |
| Predicate | railwaySignage |
P50536
|
FINISHED |
| Object | S-Bahn logo |
—
|
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: S-Bahn logo | Statement: [S-Bahn Luzern, railwaySignage, S-Bahn logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwaySignage Context triple: [S-Bahn Luzern, railwaySignage, S-Bahn logo]
-
A.
railwaySign
chosen
Indicates that one entity functions as a railway-related sign or signal that conveys information or instructions within a rail transport context to another entity.
-
B.
railwaySignColor
Indicates the color attribute assigned to a particular railway sign.
-
C.
railwaySignificance
Indicates the importance or role that a railway or rail-related feature has within a transportation network, region, or context.
-
D.
usesRailwaySignallingSystem
Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
-
E.
railwayHeritageFeature
Indicates that something is a feature associated with railway heritage, such as historically significant railway structures, equipment, or related elements.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b59ae2c8190bfa26a3f1e59b8d1 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.