Triple
T16342954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springer Mountain Shelter |
E396852
|
entity |
| Predicate | nearbyTrailTerminus |
P104127
|
FINISHED |
| Object | southern terminus of the Appalachian Trail |
—
|
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: southern terminus of the Appalachian Trail | Statement: [Springer Mountain Shelter, nearbyTrailTerminus, southern terminus of the Appalachian Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTrailTerminus Context triple: [Springer Mountain Shelter, nearbyTrailTerminus, southern terminus of the Appalachian Trail]
-
A.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
nearbyTerminus
chosen
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
D.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0b88d081908a99cafa8e0ae5db |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.