Triple
T8891578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavinger House |
E211688
|
entity |
| Predicate | NRHPDelistingDate |
P85567
|
FINISHED |
| Object | 2017-03-07 |
—
|
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: 2017-03-07 | Statement: [Bavinger House, NRHPDelistingDate, 2017-03-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPDelistingDate Context triple: [Bavinger House, NRHPDelistingDate, 2017-03-07]
-
A.
NRHPListingDate
Indicates the date on which something was officially listed in the National Register of Historic Places.
-
B.
NRHPListingReason
Indicates the reason or justification for a property's inclusion in the National Register of Historic Places (NRHP).
-
C.
NRHPReferenceNumber
Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
-
D.
designatedNRHP
Indicates that an entity has been formally designated and listed on the National Register of Historic Places (NRHP).
-
E.
NationalHistoricLandmarkDesignationDate
Indicates the date on which something was officially designated as a National Historic Landmark.
- F. None of above. chosen
Provenance (4 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61ba33c48190a657fc4147a326c0 |
completed | April 1, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:54 p.m.