Triple
T35601648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hofje van Bakenes |
E1028772
|
entity |
| Predicate | heritageRegisterId |
P1487
|
FINISHED |
| Object | 19225 |
—
|
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: 19225 | Statement: [Hofje van Bakenes, heritageRegisterId, 19225]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageRegisterId Context triple: [Hofje van Bakenes, heritageRegisterId, 19225]
-
A.
heritageId
Indicates that one entity serves as the heritage identifier or heritage reference code associated with another entity.
-
B.
heritageDesignationNumber
chosen
Indicates the specific official identification number assigned to an entity as part of its heritage or cultural protection designation.
-
C.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
-
D.
heritageDesignationSystem
Indicates the formal heritage classification or protection system under which an entity has been designated.
-
E.
heritageProtectionAuthority
Indicates that an entity serves as the official body responsible for protecting, managing, or regulating cultural or natural heritage.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:05 p.m.