Triple
T26468614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randolph Mountain Club trail system |
E665837
|
entity |
| Predicate | hasTrailheadAlong |
P62103
|
FINISHED |
| Object | U.S. Route 2 in New Hampshire |
—
|
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: U.S. Route 2 in New Hampshire | Statement: [Randolph Mountain Club trail system, hasTrailheadAlong, U.S. Route 2 in New Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailheadAlong Context triple: [Randolph Mountain Club trail system, hasTrailheadAlong, U.S. Route 2 in New Hampshire]
-
A.
hasTrailheadAt
Indicates that a trail or route begins or has its official starting point at a specified location.
-
B.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
C.
hasTrailheads
chosen
Indicates that one location or area contains or provides access points where trails begin.
-
D.
hasTrailheadFacility
Indicates that a location provides a designated starting-point facility or infrastructure for accessing a trail.
-
E.
hasTrailheadBelow
Indicates that the starting point of a trail is located at a lower elevation or position relative to another referenced feature or location.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 12:17 a.m.