Triple
T38288447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilnualna Falls trailhead near Wawona |
E1022285
|
entity |
| Predicate | accessRequiresEntranceFee |
P113361
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chilnualna Falls trailhead near Wawona, accessRequiresEntranceFee, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessRequiresEntranceFee Context triple: [Chilnualna Falls trailhead near Wawona, accessRequiresEntranceFee, yes]
-
A.
admissionFee
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
B.
parkEntryRequired
Indicates that access to a park is conditional on meeting an entry requirement, such as paying a fee, having a permit, or possessing valid authorization.
-
C.
hasAttractionAccess
Indicates that an entity has permission or the ability to enter, use, or benefit from a specified attraction.
-
D.
accessibleWithoutParkTicket
Indicates that a location, attraction, or service can be reached or used without requiring a park admission ticket.
-
E.
feeAccess
chosen
Indicates that access to something is granted only upon payment of a fee or charge.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.