Triple
T12787581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunham Massey |
E305670
|
entity |
| Predicate | hasBuildingStartDate |
P106367
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Dunham Massey, hasBuildingStartDate, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingStartDate Context triple: [Dunham Massey, hasBuildingStartDate, 18th century]
-
A.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
B.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
C.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
D.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
E.
startOfConstructionApprox
chosen
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5dbdb88190a1b06721ada51627 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.