Triple
T10300728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sint-Omaars |
E241619
|
entity |
| Predicate | heeftHistorischErfgoed |
P79036
|
FINISHED |
| Object | middeleeuwseBinnenstad |
—
|
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: middeleeuwseBinnenstad | Statement: [Sint-Omaars, heeftHistorischErfgoed, middeleeuwseBinnenstad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heeftHistorischErfgoed Context triple: [Sint-Omaars, heeftHistorischErfgoed, middeleeuwseBinnenstad]
-
A.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
B.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
C.
heritageProject
Indicates a project or initiative focused on preserving, restoring, or promoting cultural, historical, or natural heritage.
-
D.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
E.
heritageLocation
chosen
Indicates that a location is recognized or designated as having cultural, historical, or natural heritage significance in relation to something.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2eefe8881908a672c4dca7657ca |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:44 a.m.