Triple
T29312371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | country estate Horn |
E743271
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural property of regional significance in Switzerland |
C54810
|
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: cultural property of regional significance in Switzerland Context triple: [country estate Horn, instanceOf, cultural property of regional significance in Switzerland]
-
A.
region of Switzerland
A region of Switzerland is a geographically defined area within the country characterized by shared cultural, linguistic, economic, or natural features that distinguish it from other parts of Switzerland.
-
B.
Swiss cultural tradition
A Swiss cultural tradition is a recurring practice, custom, or celebration rooted in Switzerland’s diverse regional histories and languages that expresses shared values, identity, and social cohesion across generations.
-
C.
museum in Switzerland
A museum in Switzerland is a cultural institution that collects, preserves, researches, and exhibits artworks, historical artifacts, or scientific objects within the Swiss context for public education and enjoyment.
-
D.
district of Switzerland
A district of Switzerland is an intermediate administrative subdivision within a canton that groups several municipalities for purposes such as local governance, judicial organization, and regional coordination.
-
E.
Swiss canton code
A Swiss canton code is a standardized short alphanumeric identifier used to uniquely represent each canton within Switzerland for administrative, statistical, and legal purposes.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:17 p.m.