Triple
T3722526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litovel |
E81669
|
entity |
| Predicate | hasHistoricCenterStatus |
P51441
|
FINISHED |
| Object | urban monument zone |
—
|
LITERAL FINISHED |
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: urban monument zone | Statement: [Litovel, hasHistoricCenterStatus, urban monument zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCenterStatus Context triple: [Litovel, hasHistoricCenterStatus, urban monument zone]
-
A.
isHistoricCenterOf
Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
-
B.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
-
C.
hasHistoricCenterShape
Indicates the geometric form or configuration that characterizes the historic center of a place or settlement.
-
D.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
E.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
- F. None of above. chosen
Provenance (4 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9ea1688190b3b8414d77960e8f |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc48ec1a081909af0ff9f267c0ffe |
completed | March 8, 2026, 6:48 p.m. |
Created at: March 8, 2026, 3:34 p.m.