Triple
T16105252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkehrsbetriebe Zürich |
E390721
|
entity |
| Predicate | hasBrand |
P1500
|
FINISHED |
| Object | VBZ Zürich |
E390722
|
NE 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: VBZ Zürich | Statement: [Verkehrsbetriebe Zürich, hasBrand, VBZ Zürich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VBZ Zürich Context triple: [Verkehrsbetriebe Zürich, hasBrand, VBZ Zürich]
-
A.
VBZ
chosen
VBZ is the municipal public transport operator in Zurich, Switzerland, running the city’s trams, buses, and other local transit services.
-
B.
BVB
BVB is the public transport company that operates much of the tram and bus network in Basel, Switzerland.
-
C.
BVB
BVB is the common abbreviation for Borussia Dortmund, a major professional football club based in Dortmund, Germany.
-
D.
BVZ Holding
BVZ Holding is a Swiss transport and tourism company that operates and manages regional railways and related services in the Alpine region.
-
E.
BZV
BZV is the IATA airport code for Maya-Maya Airport, the main international airport serving Brazzaville in the Republic of the Congo.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6b91a48190a04648d4cad2c4b1 |
completed | April 17, 2026, 9:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeba1e4c08190a90f5102e0038056 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 5 a.m.