Triple
T489485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinnacles National Park |
E9953
|
entity |
| Predicate | dateEstablishedAsNationalPark |
P14062
|
FINISHED |
| Object | 2013-01-10 |
—
|
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: 2013-01-10 | Statement: [Pinnacles National Park, dateEstablishedAsNationalPark, 2013-01-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateEstablishedAsNationalPark Context triple: [Pinnacles National Park, dateEstablishedAsNationalPark, 2013-01-10]
-
A.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
B.
hasNationalSeashore
Indicates that a place or region is designated and managed as a national seashore.
-
C.
nationalMonument
Indicates that something has been officially designated as a national monument by a country or governing authority.
-
D.
isNationalMemorialOf
Indicates that a site, structure, or monument has been officially designated as a national memorial commemorating or representing a particular entity, event, or subject.
-
E.
withinNationalPark
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0e0a9648190b6a3b2da3a3b51e6 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.