Triple
T6251867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodie |
E140062
|
entity |
| Predicate | designatedStateHistoricPark |
P65128
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Bodie, designatedStateHistoricPark, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedStateHistoricPark Context triple: [Bodie, designatedStateHistoricPark, 1962]
-
A.
stateHistoricParkDesignationYear
chosen
Indicates the year in which a place or site was officially designated as a state historic park.
-
B.
hasNationalHistoricalPark
Indicates that an entity possesses or is associated with a designated National Historical Park.
-
C.
designatedAsNationalPark
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
-
D.
establishedAsNationalHistoricSite
Indicates that an entity has been officially designated and recognized as a National Historic Site by the appropriate authority.
-
E.
stateHistoricSiteManagedBy
Indicates that a designated state historic site is administered, overseen, or operated by a particular managing organization or authority.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633fb2ac8190b71b8e35fa923300 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.