Triple
T938156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topeka Cemetery |
E20244
|
entity |
| Predicate | NRHPListingStatus |
P999
|
FINISHED |
| Object | listed |
—
|
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: listed | Statement: [Topeka Cemetery, NRHPListingStatus, listed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPListingStatus Context triple: [Topeka Cemetery, NRHPListingStatus, listed]
-
A.
NRHPListingReason
Indicates the reason or justification for a property's inclusion in the National Register of Historic Places (NRHP).
-
B.
nationalRegisterOfHistoricPlacesListing
Indicates that an entity is officially listed in the National Register of Historic Places as a recognized historic property or site.
-
C.
NRHPListingDate
Indicates the date on which something was officially listed in the National Register of Historic Places.
-
D.
NRHPReferenceNumber
Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
-
E.
addedToNRHP
chosen
Indicates that something has been officially listed on the National Register of Historic Places.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.