Triple
T14607798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gage Building |
E342876
|
entity |
| Predicate | hasChicagoLandmarkDesignationDate |
P45856
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Gage Building, hasChicagoLandmarkDesignationDate, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChicagoLandmarkDesignationDate Context triple: [Gage Building, hasChicagoLandmarkDesignationDate, 1996]
-
A.
ChicagoLandmarkDesignationYear
chosen
Indicates the year in which an entity was officially designated as a Chicago landmark.
-
B.
NationalHistoricLandmarkDesignationDate
Indicates the date on which something was officially designated as a National Historic Landmark.
-
C.
designatedChicagoLandmark
Indicates that an entity has been officially recognized and designated as a Chicago landmark.
-
D.
dateOfNationalMonumentDesignation
Indicates the specific date on which something was officially designated as a national monument.
-
E.
cityLandmarkDesignationDate
Indicates the date on which a particular landmark was officially designated or recognized within a city.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44d327c8190a8d20568429d0f80 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.