Triple
T405772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaile Mansion |
E9379
|
entity |
| Predicate | dateOfHeritageDesignation |
P624
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Vaile Mansion, dateOfHeritageDesignation, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfHeritageDesignation Context triple: [Vaile Mansion, dateOfHeritageDesignation, 1969]
-
A.
heritageDesignationDate
chosen
Indicates the date on which something was formally granted a particular heritage designation or status.
-
B.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
C.
hasHeritageDesignation
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
-
D.
heritageDesignationNumber
Indicates the specific official identification number assigned to an entity as part of its heritage or cultural protection designation.
-
E.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbc00508190bbb602179273f29c |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.