Triple
T21447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Capitol |
E425
|
entity |
| Predicate | nrhpDesignationDate |
P1279
|
FINISHED |
| Object | December 19, 1960 |
—
|
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: December 19, 1960 | Statement: [United States Capitol, nrhpDesignationDate, December 19, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nrhpDesignationDate Context triple: [United States Capitol, nrhpDesignationDate, December 19, 1960]
-
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.
nationalHistoricLandmarkDesignation
Indicates that an entity has been formally designated as a National Historic Landmark by the appropriate governmental authority.
-
D.
designatedNationalHistoricLandmark
Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
-
E.
addedToNRHP
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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a24654724481909ba14b7f68d2a472 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.