Triple
T14835575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephansplatz transport hub |
E348820
|
entity |
| Predicate | servedByLine |
P1293
|
FINISHED |
| Object | U1 |
E938851
|
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: U1 | Statement: [Stephansplatz transport hub, servedByLine, U1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U1 Context triple: [Stephansplatz transport hub, servedByLine, U1]
-
A.
U1
U1 is a major line of the Nuremberg U-Bahn rapid transit system, connecting key districts across the Nuremberg metropolitan area.
-
B.
U1
U1 is one of Berlin’s oldest and most central U-Bahn lines, running predominantly east–west through inner-city districts and serving key cultural and nightlife areas.
-
C.
U1
U1 is a rapid transit line of the Frankfurt U-Bahn network in Frankfurt am Main, Germany.
-
D.
U1
U1 is a major line of the Munich U-Bahn rapid transit system, running through key districts of the city and connecting important residential and commercial areas.
-
E.
U1
chosen
U1 is a major line of the Vienna U-Bahn rapid transit system, running in a north–south direction and connecting key districts across the city.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded076ac9c8190a05cabec5e87d207 |
completed | April 14, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe38a5d8888190821988ad00351d05 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:52 a.m.