Triple
T17742082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Untertorbrücke |
E442884
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Nydeggbrü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: Nydeggbrücke | Statement: [Untertorbrücke, near, Nydeggbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nydeggbrücke Context triple: [Untertorbrücke, near, Nydeggbrücke]
-
A.
Nydegg Bridge
chosen
Nydegg Bridge is a historic stone arch bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with the eastern districts.
-
B.
Basteibrücke
Basteibrücke is a famous sandstone bridge and viewpoint in Germany’s Saxon Switzerland National Park, offering dramatic views over the Elbe River and surrounding rock formations.
-
C.
Aspernbrücke
Aspernbrücke is a bridge in Vienna, Austria, known for carrying traffic across the Danube Canal near the city center.
-
D.
Aare bridge
Aare bridge is a notable bridge spanning the Aare River in the Swiss town of Brugg, serving as a key local crossing and landmark.
-
E.
Herdbrücke
Herdbrücke is a historic bridge in Ulm, Germany, spanning the Danube and connecting the city center with the neighboring town of Neu-Ulm.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47acd780c8190b1308ef0aca00f5c |
completed | April 19, 2026, 6:48 a.m. |
Created at: April 10, 2026, 10:09 a.m.