Triple
T8148977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Muir |
E190285
|
entity |
| Predicate | requiresParkingPass |
P41508
|
FINISHED |
| Object | Mount Rainier National Park entrance fee |
—
|
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: Mount Rainier National Park entrance fee | Statement: [Camp Muir, requiresParkingPass, Mount Rainier National Park entrance fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresParkingPass Context triple: [Camp Muir, requiresParkingPass, Mount Rainier National Park entrance fee]
-
A.
requiresParkTicket
Indicates that access to something is conditional on possessing a valid park ticket.
-
B.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
C.
parkingRequirement
chosen
Indicates the specified conditions or obligations related to providing or using parking associated with an entity or activity.
-
D.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
E.
hasParkingFor
Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb447fc4308190b9436b0fe51a70a5 |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.