Triple
T36764229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Damascus, Virginia |
E908290
|
entity |
| Predicate | isTrailHubFor |
P155776
|
FINISHED |
| Object | Appalachian Trail |
—
|
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: Appalachian Trail | Statement: [Damascus, Virginia, isTrailHubFor, Appalachian Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrailHubFor Context triple: [Damascus, Virginia, isTrailHubFor, Appalachian Trail]
-
A.
isRailHubFor
Indicates that a location functions as a central node or interchange point within a rail network for the referenced area, routes, or services.
-
B.
hasTrailNetwork
Indicates that an entity possesses or is associated with a system of interconnected trails or paths.
-
C.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
D.
isProductionHubFor
Indicates that a location or facility serves as a central site where goods, services, or content are primarily produced for another entity or region.
-
E.
hasTrailCentre
chosen
Indicates that a location or area contains or is served by a designated trail centre that provides access to and facilities for trails.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.