Triple
T5014106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern Hauptbahnhof |
E112698
|
entity |
| Predicate | UICStationCode |
P1289
|
FINISHED |
| Object | 8507000 |
—
|
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: 8507000 | Statement: [Bern Hauptbahnhof, UICStationCode, 8507000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UICStationCode Context triple: [Bern Hauptbahnhof, UICStationCode, 8507000]
-
A.
hasStationCode
chosen
Indicates that an entity is associated with a specific station identification code.
-
B.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
C.
stationName
Indicates the name assigned to a particular station in the relationship.
-
D.
interchangeStation
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
-
E.
stationNumber
Indicates the specific station identifier or code assigned to an entity within a system or network.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7310c5b08190a5c9ab0f9fe9569f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.