Triple
T5247201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limmat River |
E118490
|
entity |
| Predicate | crossedBy |
P416
|
FINISHED |
| Object |
Kornhausbrücke
Kornhausbrücke is a bridge in Zurich, Switzerland, that carries traffic across the Limmat River near the city’s historic center.
|
E509435
|
NE FINISHED |
How this triple was built (4 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: Kornhausbrücke | Statement: [Limmat River, crossedBy, Kornhausbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kornhausbrücke Context triple: [Limmat River, crossedBy, Kornhausbrücke]
-
A.
Kornhausbrücke
Kornhausbrücke is a historic bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with newer districts.
-
B.
Schlossbrücke
Schlossbrücke is a historic bridge in central Berlin that spans the Spree River, connecting Unter den Linden with Museum Island near the Berlin Palace.
-
C.
Rathausbrücke
Rathausbrücke is a historic pedestrian bridge in central Zurich, Switzerland, spanning the Limmat River near the city hall and the old town.
-
D.
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.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kornhausbrücke Triple: [Limmat River, crossedBy, Kornhausbrücke]
Generated description
Kornhausbrücke is a bridge in Zurich, Switzerland, that carries traffic across the Limmat River near the city’s historic center.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Kornhausbrücke Target entity description: Kornhausbrücke is a bridge in Zurich, Switzerland, that carries traffic across the Limmat River near the city’s historic center.
-
A.
Kornhausbrücke
Kornhausbrücke is a historic bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with newer districts.
-
B.
Schlossbrücke
Schlossbrücke is a historic bridge in central Berlin that spans the Spree River, connecting Unter den Linden with Museum Island near the Berlin Palace.
-
C.
Rathausbrücke
Rathausbrücke is a historic pedestrian bridge in central Zurich, Switzerland, spanning the Limmat River near the city hall and the old town.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b5320748190bcf3be4b6c364f92 |
completed | March 20, 2026, 4:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf10cdb614819092621690e836338e |
completed | March 21, 2026, 9:42 p.m. |
| NEDg | Description generation | batch_69bf11949c8c8190ad3643d1accdf8a4 |
completed | March 21, 2026, 9:45 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf11f901e08190b1d708ed88ea7865 |
completed | March 21, 2026, 9:47 p.m. |
Created at: March 20, 2026, 1:50 p.m.