Triple
T15483920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müllerstraße |
E376992
|
entity |
| Predicate | hasU-BahnStation |
P726
|
FINISHED |
| Object | Seestraße |
E72451
|
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: Seestraße | Statement: [Müllerstraße, hasU-BahnStation, Seestraße]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seestraße Context triple: [Müllerstraße, hasU-BahnStation, Seestraße]
-
A.
Seestraße
chosen
Seestraße is a Berlin U-Bahn station on the U6 line located in the Wedding district of the city.
-
B.
Birkenstraße
Birkenstraße is a Berlin U-Bahn station on line U9 located in the Moabit district of the city.
-
C.
Munsterdamm
Munsterdamm is a street in Berlin, Germany, situated near the Insulaner hill in the city's southwestern area.
-
D.
Langenstraße
Langenstraße is a district or neighborhood within the town of Rüthen in North Rhine-Westphalia, Germany.
-
E.
Voßstraße
Voßstraße is a street in central Berlin, Germany, historically notable for hosting key government buildings of the German Empire and Nazi era near Potsdamer Platz and the government quarter.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8e6ff08190b130b3a38f4190e7 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff365b3980819094d3ca0b7766009c |
completed | May 9, 2026, 1:27 p.m. |
Created at: April 10, 2026, 3:45 a.m.