Triple
T37916171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Rock Trailhead |
E945822
|
entity |
| Predicate | accessesTrailSystem |
P93497
|
FINISHED |
| Object | Bell Rock Pathway 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: Bell Rock Pathway system | Statement: [Bell Rock Trailhead, accessesTrailSystem, Bell Rock Pathway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesTrailSystem Context triple: [Bell Rock Trailhead, accessesTrailSystem, Bell Rock Pathway system]
-
A.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
B.
hasTrailAccessPoint
chosen
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
C.
trailUses
Indicates that a trail supports or is designated for specific types of use or activities (such as hiking, biking, or horseback riding).
-
D.
isPartOfTrailSystem
Indicates that something belongs to, or is included within, a larger trail network or trail system.
-
E.
trailheadAccessRoad
Indicates the road that provides access to a specific trailhead.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.