Triple
T22015648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermannplatz station |
E543701
|
entity |
| Predicate | servedByLine |
P1293
|
FINISHED |
| Object | U8 |
—
|
NE NERFINISHED |
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: U8 | Statement: [Hermannplatz station, servedByLine, U8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U8 Context triple: [Hermannplatz station, servedByLine, U8]
-
A.
U8
chosen
U8 is a major north–south line of the Berlin U-Bahn rapid transit system, connecting districts such as Gesundbrunnen, Mitte, and Neukölln.
-
B.
U8
U8 is a former temporary line designation of the Munich U-Bahn rapid transit system, used primarily for special or reinforcement services rather than as a regular, permanent route.
-
C.
U8
U8 is a light rail line of the Stuttgart Stadtbahn network serving various districts in and around Stuttgart, Germany.
-
D.
U8
U8 is a line of the Frankfurt U-Bahn rapid transit network serving parts of Frankfurt and its surrounding areas.
-
E.
U8
U8 is the former IATA airline designator assigned to the now-defunct Armenian carrier Armavia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a774548190bcd98dc28f2d2c5f |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:22 p.m.