Triple
T16184075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schöneberg municipal railway |
E392753
|
entity |
| Predicate | operatedLine |
P848
|
FINISHED |
| Object | U4 |
E530779
|
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: U4 | Statement: [Schöneberg municipal railway, operatedLine, U4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U4 Context triple: [Schöneberg municipal railway, operatedLine, U4]
-
A.
U4
U4 is a line of the Frankfurt U-Bahn rapid transit system in Frankfurt, Germany.
-
B.
U4
U4 is a line of the Munich U-Bahn rapid transit system serving several central and eastern districts of Munich, Germany.
-
C.
U4
U4 is a light rail line of the Stuttgart Stadtbahn public transit network in Stuttgart, Germany.
-
D.
U4
U4 is one of Vienna’s main underground metro lines, running along the city’s central axis and connecting key districts and transport hubs.
-
E.
U4
chosen
U4 is one of the shortest and oldest lines of the Berlin U-Bahn, running entirely within the central district of Schöneberg.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205fc080819097858f36253fef7c |
completed | April 17, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff0550b48190ac84946b7254552b |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.