Triple
T1908063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Astrodome |
E38046
|
entity |
| Predicate | designatedHoustonLandmark |
P33867
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Houston Astrodome, designatedHoustonLandmark, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedHoustonLandmark Context triple: [Houston Astrodome, designatedHoustonLandmark, 2017]
-
A.
designatedChicagoLandmark
Indicates that an entity has been officially recognized and designated as a Chicago landmark.
-
B.
designatedNYCLandmark
Indicates that an entity has been officially designated as a New York City landmark by the appropriate municipal authority.
-
C.
designatedNationalHistoricLandmark
Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
-
D.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
E.
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.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.