Triple
T3900186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opernhaus |
E90468
|
entity |
| Predicate | servesLine |
P839
|
FINISHED |
| Object | U2 line |
E297622
|
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 line | Statement: [Opernhaus, servesLine, U2 line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U2 line Context triple: [Opernhaus, servesLine, U2 line]
-
A.
U2 line
chosen
The U2 line is a rapid transit route of the Frankfurt U-Bahn network that connects central Frankfurt with several outlying districts.
-
B.
U2
U2 is one of the main rapid transit lines of the Nuremberg U-Bahn system in Nuremberg, Germany.
-
C.
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.
-
D.
U2
U2 is the IATA airline code for easyJet, a major low-cost airline based in the United Kingdom.
-
E.
U2 360° Tour
The U2 360° Tour was a record-breaking global concert tour by the Irish rock band U2, notable for its innovative 360-degree stage design that allowed audiences to surround the band in stadiums.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecf17ef4819083db0a22e24d5b89 |
completed | March 9, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51ca477a081908b7e6d2701833413 |
completed | March 14, 2026, 8:30 a.m. |
Created at: March 9, 2026, 3:21 p.m.