Triple
T17252416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordostbahnhof station |
E418788
|
entity |
| Predicate | servedByLine |
P1293
|
FINISHED |
| Object | U2 |
E90419
|
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: U2 | Statement: [Nordostbahnhof station, servedByLine, U2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U2 Context triple: [Nordostbahnhof station, servedByLine, U2]
-
A.
U2
U2 is an Irish rock band formed in Dublin in 1976, renowned for its anthemic sound, socially conscious lyrics, and global influence on popular music.
-
B.
U2
chosen
U2 is one of the main rapid transit lines of the Nuremberg U-Bahn system in Nuremberg, Germany.
-
C.
U2
U2 is the IATA airline code for easyJet, a major low-cost airline based in the United Kingdom.
-
D.
U2
U2 is a major line of the Berlin U-Bahn rapid transit system, running east–west across the city and serving many central and historically significant stations.
-
E.
U2
U2 is one of the main lines of the Munich U-Bahn rapid transit system, 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6a1b648190a8bb2deb67bbdfdc |
completed | April 19, 2026, 1:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170fb89248190ae431ce51dfeaffd |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:39 a.m.