Triple
T454082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermeer Mill |
E7193
|
entity |
| Predicate | reflectsHeritage |
P1494
|
FINISHED |
| Object | Dutch heritage of Pella |
—
|
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: Dutch heritage of Pella | Statement: [Vermeer Mill, reflectsHeritage, Dutch heritage of Pella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsHeritage Context triple: [Vermeer Mill, reflectsHeritage, Dutch heritage of Pella]
-
A.
hasHeritage
chosen
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
heritageValue
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
-
C.
heritageField
Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
-
D.
heritageInfluence
Indicates how one entity’s cultural, historical, or ancestral background affects or shapes another entity’s characteristics, behavior, or development.
-
E.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef866e848190a5b700250ec56256 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.