Triple
T184393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Palace of Amsterdam |
E3948
|
entity |
| Predicate | heritageDesignationStart |
P624
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Royal Palace of Amsterdam, heritageDesignationStart, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageDesignationStart Context triple: [Royal Palace of Amsterdam, heritageDesignationStart, 1970s]
-
A.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
B.
heritageDesignationDate
chosen
Indicates the date on which something was formally granted a particular heritage designation or status.
-
C.
heritageDesignationNumber
Indicates the specific official identification number assigned to an entity as part of its heritage or cultural protection designation.
-
D.
hasHeritageDesignation
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
-
E.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25926be9c8190a4cfce66f57589d1 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.