Triple
T5117195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoye Crest |
E115364
|
entity |
| Predicate | trailAccessFrom |
P39694
|
FINISHED |
| Object | West Virginia side of Backbone Mountain |
—
|
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: West Virginia side of Backbone Mountain | Statement: [Hoye Crest, trailAccessFrom, West Virginia side of Backbone Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailAccessFrom Context triple: [Hoye Crest, trailAccessFrom, West Virginia side of Backbone Mountain]
-
A.
trailAssociation
chosen
Indicates an associative relationship between entities where one is contextually or functionally linked to a trail (such as being located on, connected to, or part of that trail).
-
B.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
C.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
D.
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.
-
E.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:41 p.m.