Triple
T16919880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BVG Class F |
E410417
|
entity |
| Predicate | usedOnLine |
P15252
|
FINISHED |
| Object | U8 |
E530781
|
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: U8 | Statement: [BVG Class F, usedOnLine, U8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U8 Context triple: [BVG Class F, usedOnLine, 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.
UB8
UB8 is a postal district in the UB (Southall and Uxbridge) postcode area of west London, covering parts of Uxbridge and its surroundings.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c7c2c9cc8190b6d59d0a8edd078d |
completed | May 10, 2026, 6 p.m. |
Created at: April 10, 2026, 5:30 a.m.