Triple
T16129190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abingdon, Virginia |
E391348
|
entity |
| Predicate | VirginiaCreeperTrailUse |
P121589
|
FINISHED |
| Object | hiking |
—
|
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: hiking | Statement: [Abingdon, Virginia, VirginiaCreeperTrailUse, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VirginiaCreeperTrailUse Context triple: [Abingdon, Virginia, VirginiaCreeperTrailUse, hiking]
-
A.
visionForAppalachianTrail
Indicates a stated plan, goal, or long-term vision concerning the future condition, use, or management of the Appalachian Trail.
-
B.
roleInAppalachianTrail
Indicates a relationship where an entity holds a specific role, function, or responsibility in connection with the Appalachian Trail.
-
C.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
D.
northeastTrailStatus
Indicates the current condition or accessibility state of trails located in the northeast region.
-
E.
isPartOfTrailSystem
Indicates that something belongs to, or is included within, a larger trail network or trail system.
- F. None of above. chosen
Provenance (4 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e202075860819088d27d921609a6ce |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5:01 a.m.