Triple
T25077069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Rock |
E628078
|
entity |
| Predicate | designatedAsNationalNaturalLandmark |
P84242
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [Fort Rock, designatedAsNationalNaturalLandmark, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsNationalNaturalLandmark Context triple: [Fort Rock, designatedAsNationalNaturalLandmark, 1966]
-
A.
designatedAsNationalPark
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
-
B.
nationalNaturalLandmarkDesignationYear
chosen
Indicates the year in which a place or feature was officially designated as a National Natural Landmark.
-
C.
establishedAsNationalParkBy
Indicates that an area or site was officially designated and created as a national park through the action or authority of a specific person, organization, or governmental body.
-
D.
nationalParkName
Indicates the name assigned to a national park.
-
E.
nationalPark
Indicates that a location is designated and managed as a national park by a governing 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:21 a.m.