Triple
T15461871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avon Wilderness Park |
E371920
|
entity |
| Predicate | visitorAccessLevel |
P101786
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Avon Wilderness Park, visitorAccessLevel, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorAccessLevel Context triple: [Avon Wilderness Park, visitorAccessLevel, low]
-
A.
visitorAccessibility
Indicates how easily or suitably a place, service, or resource can be used or reached by visitors, including those with varying needs or abilities.
-
B.
visitorUseLevel
chosen
Indicates the intensity or frequency with which visitors use or occupy a particular place, resource, or service.
-
C.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
D.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
E.
visitorAccessPoint
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.