Triple
T17582303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America Hill Trail |
E428232
|
entity |
| Predicate | hasClimb |
P128091
|
FINISHED |
| Object | moderate elevation gain |
—
|
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: moderate elevation gain | Statement: [America Hill Trail, hasClimb, moderate elevation gain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimb Context triple: [America Hill Trail, hasClimb, moderate elevation gain]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
C.
hasClimbFrom
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
-
D.
hasNearbyClimb
Indicates that one location or entity is situated close to a climbable feature or climbing route.
-
E.
hasClimbSide
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
- F. None of above. chosen
Provenance (4 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463cf556881908d2935b3761f65df |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.