Triple
T14405342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-Bahnhof Seestraße |
E357181
|
entity |
| Predicate | terminusOf |
P3375
|
FINISHED |
| Object | U6 |
E71188
|
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: U6 | Statement: [U-Bahnhof Seestraße, terminusOf, U6]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U6 Context triple: [U-Bahnhof Seestraße, terminusOf, U6]
-
A.
U6
chosen
U6 is a major north–south line of the Berlin U-Bahn rapid transit system, connecting several key districts across the city.
-
B.
U6
U6 is a major Munich U-Bahn line running north–south across the city, connecting key districts and transport hubs.
-
C.
U6
U6 is the IATA airline designator assigned to Ural Airlines, a Russian commercial air carrier.
-
D.
U6
U6 is a light rail line of the Stuttgart Stadtbahn network serving various districts in and around Stuttgart, Germany.
-
E.
U6
U6 is a rapid transit line of the Frankfurt U-Bahn system serving 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908804048190a4fe58afc2e0a5b6 |
completed | April 14, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6485d4c48190ac67fd43834aa803 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:17 a.m.