Triple
T508511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Cultural Center |
E10553
|
entity |
| Predicate | landmarkDesignationYear |
P13050
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Chicago Cultural Center, landmarkDesignationYear, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landmarkDesignationYear Context triple: [Chicago Cultural Center, landmarkDesignationYear, 1976]
-
A.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
B.
monumentProclamationYear
Indicates the year in which a monument was officially proclaimed or designated as such.
-
C.
heritageDesignationYear
chosen
Indicates the year in which something was formally granted a particular heritage designation or status.
-
D.
designatedNationalHistoricLandmark
Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
-
E.
nationalHistoricLandmarkDesignationAuthority
Indicates the entity that has the official authority to designate something as a National Historic Landmark.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f162f3888190b057ad04e40a30e2 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.