Triple
T22669310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basler Verkehrs-Betriebe |
E559877
|
entity |
| Predicate | hasMainDepot |
P86339
|
FINISHED |
| Object | Wiesenplatz depot |
—
|
NE NERFINISHED |
How this triple was built (4 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: Wiesenplatz depot | Statement: [Basler Verkehrs-Betriebe, hasMainDepot, Wiesenplatz depot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wiesenplatz depot Context triple: [Basler Verkehrs-Betriebe, hasMainDepot, Wiesenplatz depot]
-
A.
Britz-Süd depot
Britz-Süd depot is a maintenance and storage facility for trains of Berlin’s U7 underground line, located near the Britz-Süd station in the Neukölln district.
-
B.
Fürth depot
Fürth depot is a maintenance and storage facility serving the Nuremberg U-Bahn rapid transit system in the Fürth area of Germany.
-
C.
Seestraße depot
Seestraße depot is a major maintenance and storage facility for trains on Berlin’s U-Bahn rapid transit network.
-
D.
Hagenholz depot
Hagenholz depot is a major maintenance and storage facility for trolleybuses serving the Zürich public transport network.
-
E.
Grunewald depot
Grunewald depot is a major maintenance and storage facility for Berlin’s U-Bahn trains, located in the Grunewald area of the city.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Wiesenplatz depot Target entity description: Wiesenplatz depot is a major tram and bus maintenance and operations facility serving the public transport network of Basel, Switzerland.
-
A.
Britz-Süd depot
Britz-Süd depot is a maintenance and storage facility for trains of Berlin’s U7 underground line, located near the Britz-Süd station in the Neukölln district.
-
B.
Fürth depot
Fürth depot is a maintenance and storage facility serving the Nuremberg U-Bahn rapid transit system in the Fürth area of Germany.
-
C.
Seestraße depot
Seestraße depot is a major maintenance and storage facility for trains on Berlin’s U-Bahn rapid transit network.
-
D.
Hagenholz depot
Hagenholz depot is a major maintenance and storage facility for trolleybuses serving the Zürich public transport network.
-
E.
Grunewald depot
Grunewald depot is a major maintenance and storage facility for Berlin’s U-Bahn trains, located in the Grunewald area of the city.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainDepot Context triple: [Basler Verkehrs-Betriebe, hasMainDepot, Wiesenplatz depot]
-
A.
hasMainEdifice
Indicates that an entity possesses or is associated with a primary or principal building or structure.
-
B.
depot
Indicates that an entity serves as a storage or distribution center location for another entity, such as goods, vehicles, or resources.
-
C.
depotFor
chosen
Indicates that one entity serves as a storage or distribution center location dedicated to supporting or supplying another entity.
-
D.
usedInDepot
Indicates that something is utilized or operated within the context of a specific depot or storage facility.
-
E.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781ed50c8190a6943f51d7337b49 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.