Triple
T31255784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiftcurrent Glacier |
E796965
|
entity |
| Predicate | inUSNationalParkSystemUnit |
P2851
|
FINISHED |
| Object | Glacier National Park |
—
|
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: Glacier National Park | Statement: [Swiftcurrent Glacier, inUSNationalParkSystemUnit, Glacier National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUSNationalParkSystemUnit Context triple: [Swiftcurrent Glacier, inUSNationalParkSystemUnit, Glacier National Park]
-
A.
hasNationalParkServiceUnitCode
Indicates that an entity is associated with a specific National Park Service unit, identified by its official unit code.
-
B.
nationalParkName
Indicates the name assigned to a national park.
-
C.
nationalPark
chosen
Indicates that a location is designated and managed as a national park by a governing authority.
-
D.
onlyNationalParkOf
Indicates that one entity is the sole national park associated with, or located within, a given region or jurisdiction.
-
E.
designatedAsNationalPark
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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:12 p.m.