Triple
T21513145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U1 |
E530776
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Möckernbrücke |
E364626
|
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: Möckernbrücke | Statement: [U1, hasStation, Möckernbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Möckernbrücke Context triple: [U1, hasStation, Möckernbrücke]
-
A.
Möckernbrücke
chosen
Möckernbrücke is a Berlin U-Bahn station and major interchange point located near the Landwehr Canal in the Kreuzberg district.
-
B.
Kornhausbrücke
Kornhausbrücke is a historic bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with newer districts.
-
C.
Kornhausbrücke
Kornhausbrücke is a bridge in Zurich, Switzerland, that carries traffic across the Limmat River near the city’s historic center.
-
D.
Glienicker Brücke
Glienicker Brücke is a historic bridge in Berlin, Germany, famously known as the “Bridge of Spies” for its role as a Cold War site of prisoner exchanges between East and West.
-
E.
Alte Brücke
Alte Brücke is a historic stone bridge in Saarbrücken, Germany, known as one of the city’s oldest architectural landmarks spanning the Saar River.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea8779c081908171c58d345d54ae |
completed | April 23, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09e145ac5c8190a05cc2a80d28cac3 |
completed | May 17, 2026, 3:39 p.m. |
Created at: April 16, 2026, 6:25 p.m.