Triple
T38639125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of the Immaculate Conception (Linz) |
E938542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark in Linz |
C65788
|
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: landmark in Linz Context triple: [Cathedral of the Immaculate Conception (Linz), instanceOf, landmark in Linz]
-
A.
landmark in Vienna
A landmark in Vienna is a notable physical site or structure—such as a historic building, monument, or public space—that holds cultural, historical, or architectural significance and serves as a recognizable point of reference within the city.
-
B.
bridge in Salzburg
A bridge in Salzburg is a structural crossing over the Salzach River or other local waterways that connects different parts of the city and often serves as both a transportation route and a scenic vantage point.
-
C.
landmark in Dresden
A landmark in Dresden is a notable, historically or culturally significant site or structure within the city that serves as a recognizable point of reference for residents and visitors.
-
D.
Landmark in Meissen
A "Landmark in Meissen" represents any notable, historically or culturally significant site, structure, or natural feature within the city of Meissen that serves as a recognizable point of reference or attraction.
-
E.
landmark in Prague
A landmark in Prague is a notable physical site or structure—such as a historic building, bridge, square, or monument—recognized for its cultural, architectural, or historical significance within the city.
- F. None of above. chosen
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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.