Triple
T21513151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U1 |
E530776
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Uhlandstraße |
—
|
NE NERFINISHED |
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: Uhlandstraße | Statement: [U1, hasStation, Uhlandstraße]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uhlandstraße Context triple: [U1, hasStation, Uhlandstraße]
-
A.
Uhlandstraße
chosen
Uhlandstraße is a Berlin U-Bahn station located in the Charlottenburg district, known for serving the Kurfürstendamm shopping area.
-
B.
Hermannstraße
Hermannstraße is a Berlin railway and U-Bahn station in the Neukölln district that serves as a key interchange point on the city’s Ringbahn network.
-
C.
Bergmannstraße
Bergmannstraße is a notable street in Berlin, Germany, known for its lively mix of cafés, shops, and historic sites including the Luisenstädtischer Friedhof cemetery.
-
D.
Adalbertstraße
Adalbertstraße is a street in the Frankfurt district of Bockenheim, known for its urban residential character and proximity to local shops and amenities.
-
E.
Grunerstraße
Grunerstraße is a central street in Berlin located near Alexanderplatz, known for carrying heavy traffic through the city’s Mitte district.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea8779c081908171c58d345d54ae |
completed | April 23, 2026, 9:46 a.m. |
Created at: April 16, 2026, 6:25 p.m.