Triple
T5639849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esherick House |
E124237
|
entity |
| Predicate | yearListedAsHistoricPlace |
P53609
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Esherick House, yearListedAsHistoricPlace, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearListedAsHistoricPlace Context triple: [Esherick House, yearListedAsHistoricPlace, 2009]
-
A.
nationalRegisterOfHistoricPlacesListingYear
chosen
Indicates the year in which an entity was officially listed in the National Register of Historic Places.
-
B.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
C.
nationalRegisterOfHistoricPlacesListing
Indicates that an entity is officially listed in the National Register of Historic Places as a recognized historic property or site.
-
D.
NationalHistoricLandmarkDesignationDate
Indicates the date on which something was officially designated as a National Historic Landmark.
-
E.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022850bf08190953cd5394f821801 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.