Triple
T36478741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glade Spring, Virginia |
E898745
|
entity |
| Predicate | hasParkOrTrailAccess |
P93497
|
FINISHED |
| Object | Virginia Creeper Trail (nearby) |
—
|
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: Virginia Creeper Trail (nearby) | Statement: [Glade Spring, Virginia, hasParkOrTrailAccess, Virginia Creeper Trail (nearby)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkOrTrailAccess Context triple: [Glade Spring, Virginia, hasParkOrTrailAccess, Virginia Creeper Trail (nearby)]
-
A.
hasBikeTrailAccess
Indicates that an entity has direct access to, or is connected with, a bike trail suitable for cycling.
-
B.
hasHikingAccess
Indicates that one location or entity provides access or a connection to hiking trails or hiking areas.
-
C.
hasScenicAccessTo
Indicates that one place or object provides a visually appealing or notable view of another place or object.
-
D.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
E.
hasTrailAccessPoint
chosen
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:10 p.m.