Triple
T35023484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid Peak (Pickets) |
E1010259
|
entity |
| Predicate | inNationalParkSystem |
P38404
|
FINISHED |
| Object | U.S. National Park System |
—
|
NE NERFINISHED |
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: U.S. National Park System | Statement: [Pyramid Peak (Pickets), inNationalParkSystem, U.S. National Park System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inNationalParkSystem Context triple: [Pyramid Peak (Pickets), inNationalParkSystem, U.S. National Park System]
-
A.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
B.
nationalParkAccess
Indicates that one entity has the right, ability, or permission to enter, use, or benefit from a specified national park.
-
C.
stateParkSystem
Indicates that an entity is part of, managed by, or associated with a state-level park system or network of state parks.
-
D.
nationalParkName
Indicates the name assigned to a national park.
-
E.
designatedAsNationalPark
chosen
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.