Triple
T34455840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Mountain, Minnesota |
E884500
|
entity |
| Predicate | hasDesignatedTrailhead |
P62103
|
FINISHED |
| Object | Eagle Mountain trailhead |
—
|
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: Eagle Mountain trailhead | Statement: [Eagle Mountain, Minnesota, hasDesignatedTrailhead, Eagle Mountain trailhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignatedTrailhead Context triple: [Eagle Mountain, Minnesota, hasDesignatedTrailhead, Eagle Mountain trailhead]
-
A.
hasTrailheads
chosen
Indicates that one location or area contains or provides access points where trails begin.
-
B.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
C.
hasTrailheadSignage
Indicates that a trailhead is equipped with signage providing information or guidance to users.
-
D.
reachableFromTrailhead
Indicates that a location or segment can be accessed by traveling from a designated trailhead.
-
E.
isOnOfficialTrailSystem
Indicates that something is located on, follows, or is part of an officially designated and maintained trail network.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 1, 2026, 2 a.m.