Triple
T20986441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaltbommel |
E516902
|
entity |
| Predicate | hasMedievalCityCenter |
P142378
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zaltbommel, hasMedievalCityCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalCityCenter Context triple: [Zaltbommel, hasMedievalCityCenter, true]
-
A.
hasHistoricCenterStatus
Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
-
B.
hasMedievalBuilding
Indicates that one entity possesses, contains, or includes a building dating from the medieval period.
-
C.
majorMedievalCity
Indicates that a location was a significant and influential urban center during the medieval period.
-
D.
isHistoricCenterOf
Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
-
E.
hasHistoricCenterShape
Indicates the geometric form or configuration that characterizes the historic center of a place or settlement.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe31cec8190a1007414148b8abe |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:49 p.m.