Triple
T23854023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown Building |
E592252
|
entity |
| Predicate | nycLandmarkDesignationYear |
P79776
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Brown Building, nycLandmarkDesignationYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nycLandmarkDesignationYear Context triple: [Brown Building, nycLandmarkDesignationYear, 2003]
-
A.
designatedNYCLandmark
Indicates that an entity has been officially designated as a New York City landmark by the appropriate municipal authority.
-
B.
NYCLandmarkID
Indicates that an entity has been designated as a New York City landmark and is associated with a specific official NYC landmark identification number.
-
C.
NYCLDesignationYear
chosen
Indicates the year in which an entity was officially designated under the New York City Landmarks (NYCL) program.
-
D.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98954748190b39e0ac69e5625f9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.