Triple
T16198553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prinzenstraße |
E393134
|
entity |
| Predicate | servesLine |
P839
|
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: [Prinzenstraße, servesLine, U1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U1 Context triple: [Prinzenstraße, servesLine, 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 a major line of the Vienna U-Bahn rapid transit system, running in a north–south direction and connecting key districts across the city.
-
C.
U1
U1 is a rapid transit line of the Frankfurt U-Bahn network in Frankfurt am Main, Germany.
-
D.
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.
-
E.
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.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222dc6b1c8190a3d8a6451ed8b95a |
completed | April 17, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff1107908190afda091b53317d81 |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 10, 2026, 5:03 a.m.