Triple
T1413180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Rainier |
E31848
|
entity |
| Predicate | nationalParkEstablished |
P14062
|
FINISHED |
| Object | 1899 |
—
|
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: 1899 | Statement: [Mount Rainier, nationalParkEstablished, 1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalParkEstablished Context triple: [Mount Rainier, nationalParkEstablished, 1899]
-
A.
dateEstablishedAsNationalPark
chosen
Indicates the date on which a location or area was officially designated as a national park.
-
B.
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.
-
C.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
D.
nationalMonument
Indicates that something has been officially designated as a national monument by a country or governing authority.
-
E.
hasNationalParkSystem
Indicates that a country or region maintains an organized, officially designated system of national parks under its governance.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e476f08190aed1576805c62462 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.