Triple
T3582847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olvera Street |
E75840
|
entity |
| Predicate | openedAsHistoricSite |
P49869
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Olvera Street, openedAsHistoricSite, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsHistoricSite Context triple: [Olvera Street, openedAsHistoricSite, 1930]
-
A.
openedAsStateHistoricPark
Indicates that an entity was officially opened or designated as a state historic park.
-
B.
establishedAsNationalHistoricSite
Indicates that an entity has been officially designated and recognized as a National Historic Site by the appropriate authority.
-
C.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
D.
openedAsStatePark
Indicates that a location or area was officially inaugurated and made available to the public as a state park.
-
E.
convertedToNationalHistoricalPark
Indicates that something previously designated under a different status (such as a monument or site) has been officially reclassified as a National Historical Park.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc104846c81908b6fbde7061464b4 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:21 p.m.