Triple
T21513338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U8 |
E530781
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Jannowitzbrücke |
—
|
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: Jannowitzbrücke | Statement: [U8, hasStation, Jannowitzbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jannowitzbrücke Context triple: [U8, hasStation, Jannowitzbrücke]
-
A.
Jannowitzbrücke
chosen
Jannowitzbrücke is a Berlin U-Bahn and S-Bahn station located near the River Spree in the city center, serving as a key transit point on several urban rail lines.
-
B.
Kaisermühlenbrücke
Kaisermühlenbrücke is a bridge in the Kaisermühlen district of Vienna, Austria, serving as a key crossing over the Danube.
-
C.
Hardbrücke
Hardbrücke is a major road and railway bridge in Zurich, Switzerland, serving as an important traffic artery across the Limmat and nearby rail tracks.
-
D.
Ludwigsbrücke
Ludwigsbrücke is a historic bridge in Munich, Germany, spanning the Isar River and connecting the city center with the eastern districts.
-
E.
Glienicke Bridge, Berlin
Glienicke Bridge in Berlin is a historic span over the Havel River that became famous during the Cold War as a key site for high-profile prisoner exchanges between East and West.
- 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_69e9ea88e6fc8190a4b73b8d32dae5a8 |
completed | April 23, 2026, 9:46 a.m. |
Created at: April 16, 2026, 6:25 p.m.