Triple
T16687044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williamson, West Virginia |
E405488
|
entity |
| Predicate | hostsTrailSystem |
P62103
|
FINISHED |
| Object | access point to Hatfield–McCoy ATV trails |
—
|
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: access point to Hatfield–McCoy ATV trails | Statement: [Williamson, West Virginia, hostsTrailSystem, access point to Hatfield–McCoy ATV trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsTrailSystem Context triple: [Williamson, West Virginia, hostsTrailSystem, access point to Hatfield–McCoy ATV trails]
-
A.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
B.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
C.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
-
D.
hasTrailheads
chosen
Indicates that one location or area contains or provides access points where trails begin.
-
E.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea63b7081908a055036172f9683 |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.