Triple
T4260289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldorf-Astoria Hotel |
E96085
|
entity |
| Predicate | cityLandmarkDesignationDate |
P55004
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Waldorf-Astoria Hotel, cityLandmarkDesignationDate, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityLandmarkDesignationDate Context triple: [Waldorf-Astoria Hotel, cityLandmarkDesignationDate, 1993]
-
A.
dateOfNationalMonumentDesignation
Indicates the specific date on which something was officially designated as a national monument.
-
B.
NationalHistoricLandmarkDesignationDate
Indicates the date on which something was officially designated as a National Historic Landmark.
-
C.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
D.
designatedNationalHistoricLandmark
Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
-
E.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular city.
- F. None of above. chosen
Provenance (4 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f8103b48190934a810faafa6cb7 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.