Triple
T15309434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U7 |
E365989
|
entity |
| Predicate | depot |
P14646
|
FINISHED |
| Object | Britz-Süd depot |
E410416
|
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: Britz-Süd depot | Statement: [U7, depot, Britz-Süd depot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Britz-Süd depot Context triple: [U7, depot, Britz-Süd depot]
-
A.
Britz-Süd depot
chosen
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.
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.
-
E.
Elsau depot
Elsau depot is a tram maintenance and storage facility serving the Strasbourg tramway network in Strasbourg, France.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd176708190b0f6ba17aed92f8e |
completed | April 16, 2026, 1:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8a20c1881909b387aed6f532c3d |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.