Triple
T9470785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schweizer Platz station |
E228382
|
entity |
| Predicate | servedByLine |
P1293
|
FINISHED |
| Object | U1 |
E530776
|
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: [Schweizer Platz station, servedByLine, U1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U1 Context triple: [Schweizer Platz station, servedByLine, U1]
-
A.
U1
chosen
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.
-
B.
U1
U1 is a major line of the Nuremberg U-Bahn rapid transit system, connecting key districts across the Nuremberg metropolitan area.
-
C.
U5
U5 is one of the lines of the Frankfurt U-Bahn rapid transit system in Frankfurt, Germany.
-
D.
U5
U5 is a major line of the Berlin U-Bahn rapid transit system that runs east–west across the city, connecting central Berlin with several eastern districts.
-
E.
U6
U6 is a major Munich U-Bahn line running north–south across the city, connecting key districts and transport hubs.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fee13a88190b4532fb92ddaf401 |
completed | April 1, 2026, 8:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d122cd0728819088f6c832cd90d832 |
completed | April 4, 2026, 2:40 p.m. |
Created at: March 30, 2026, 7:53 p.m.