Triple
T25759564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Theatre |
E648703
|
entity |
| Predicate | recordedTexasHistoricLandmarkNumber |
P165323
|
FINISHED |
| Object | 14006 |
—
|
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: 14006 | Statement: [Texas Theatre, recordedTexasHistoricLandmarkNumber, 14006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedTexasHistoricLandmarkNumber Context triple: [Texas Theatre, recordedTexasHistoricLandmarkNumber, 14006]
-
A.
recordedTexasHistoricLandmarkDesignationYear
Indicates the year in which a Texas Historic Landmark designation was officially recorded for an entity.
-
B.
texasStateAntiquitiesLandmarkDesignationYear
Indicates the year in which an entity was designated as a Texas State Antiquities Landmark.
-
C.
designatedHoustonLandmark
Indicates that an entity has been officially recognized or designated as a landmark located in Houston.
-
D.
CaliforniaHistoricalLandmarkNumber
Indicates that an entity has been assigned a specific official California Historical Landmark identification number.
-
E.
significanceInTexas
Indicates that something holds particular importance, influence, or relevance within the context or boundaries of Texas.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 22, 2026, 4:44 a.m.