Triple
T30850150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Šumperk District |
E785756
|
entity |
| Predicate | containsCulturalMonument |
P11933
|
FINISHED |
| Object | Velké Losiny Chateau |
—
|
NE NERFINISHED |
How this triple was built (2 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: Velké Losiny Chateau | Statement: [Šumperk District, containsCulturalMonument, Velké Losiny Chateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCulturalMonument Context triple: [Šumperk District, containsCulturalMonument, Velké Losiny Chateau]
-
A.
containsCulturalHeritageSite
chosen
Indicates that a place or area includes within its boundaries at least one recognized cultural heritage site.
-
B.
hasMainCulturalProperty
Indicates that an entity possesses a primary or most significant cultural property associated with it.
-
C.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
-
D.
isCulturalHeritageSite
Indicates that a place or structure is officially recognized and protected as having significant cultural, historical, or artistic value.
-
E.
hasCulturalHeritageOn
Indicates that one entity possesses, preserves, or is associated with the cultural heritage embodied in another entity.
- F. None of above.
Provenance (3 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 29, 2026, 8:46 p.m.