Triple
T35023609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Beaver Creek |
E1010262
|
entity |
| Predicate | usedAsApproachRouteFor |
P138195
|
FINISHED |
| Object | mountaineering in the Picket Range |
—
|
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: mountaineering in the Picket Range | Statement: [Big Beaver Creek, usedAsApproachRouteFor, mountaineering in the Picket Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsApproachRouteFor Context triple: [Big Beaver Creek, usedAsApproachRouteFor, mountaineering in the Picket Range]
-
A.
usedToApproach
chosen
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
B.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
C.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
D.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
E.
usesFormerRouteOf
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:01 p.m.