Triple
T203707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton Battlefield State Park |
E4562
|
entity |
| Predicate | NRHPDesignationDate |
P1279
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Princeton Battlefield State Park, NRHPDesignationDate, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPDesignationDate Context triple: [Princeton Battlefield State Park, NRHPDesignationDate, 1961]
-
A.
NRHPListingDate
chosen
Indicates the date on which something was officially listed in the National Register of Historic Places.
-
B.
heritageDesignationDate
Indicates the date on which something was formally granted a particular heritage designation or status.
-
C.
NRHPReferenceNumber
Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
-
D.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
E.
designatedNationalHistoricLandmark
Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.