Triple
T23345494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altstetten tram stop |
E591848
|
entity |
| Predicate | servedByTransportOperator |
P14525
|
FINISHED |
| Object | Verkehrsbetriebe Zürich |
—
|
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: Verkehrsbetriebe Zürich | Statement: [Altstetten tram stop, servedByTransportOperator, Verkehrsbetriebe Zürich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByTransportOperator Context triple: [Altstetten tram stop, servedByTransportOperator, Verkehrsbetriebe Zürich]
-
A.
servedByTransportation
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
-
B.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
C.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
D.
transportationServedBy
chosen
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
E.
transportOperator
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983697408190b31817174ed4e77b |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.