Triple
T25619831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allende-Brücke |
E642263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Berlin |
C19713
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: bridge in Berlin Context triple: [Allende-Brücke, instanceOf, bridge in Berlin]
-
A.
bridge in Germany
chosen
A bridge in Germany is a structural construction that spans physical obstacles such as rivers, valleys, or roads within German territory, facilitating transportation and connectivity while often reflecting the country's engineering standards and regional architectural styles.
-
B.
bridge in Stockholm
A bridge in Stockholm is a structural crossing that connects the city’s many islands and shores, facilitating transportation and integrating its urban and waterfront landscapes.
-
C.
section of the Berlin Wall
A section of the Berlin Wall is a preserved or reconstructed fragment of the former fortified barrier that once divided East and West Berlin, serving as a historical artifact and symbol of Cold War division and reunification.
-
D.
bridge over the Main
A bridge over the Main is a structural crossing that spans the Main River to connect its opposite banks for transportation and passage.
-
E.
bridge in Moscow
A bridge in Moscow is a structural crossing over the Moskva River or other waterways in the city, serving both transportation needs and often acting as an architectural landmark within the urban landscape.
- F. None of above.
Provenance (1 batch)
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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:03 p.m.