Triple
T30777226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Benedict’s Church (near Krakus Mound) |
E783708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark in Kraków |
C38031
|
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 Kraków Context triple: [St. Benedict’s Church (near Krakus Mound), instanceOf, landmark in Kraków]
-
A.
landmark of Kraków
chosen
A landmark of Kraków is a notable physical site, structure, or monument within the city that holds historical, cultural, architectural, or social significance and serves as a recognizable point of reference for residents and visitors.
-
B.
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.
-
C.
district of Kraków
A district of Kraków is an administrative subdivision of the city that encompasses specific neighborhoods, local governance structures, and public services within its defined boundaries.
-
D.
city in Poland
A city in Poland is an urban settlement within Polish territory that serves as a local administrative, economic, cultural, and social center, typically granted municipal rights under Polish law.
-
E.
landmark in the Czech Republic
A landmark in the Czech Republic is a notable natural or man-made feature, such as a historic building, monument, or geographic site, that holds cultural, historical, or architectural significance and serves as a recognizable point of interest within the country.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:41 p.m.