Triple
T2693718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freerider |
E58462
|
entity |
| Predicate | cliffHeightCategory |
P35392
|
FINISHED |
| Object | over 900 meters |
—
|
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: over 900 meters | Statement: [Freerider, cliffHeightCategory, over 900 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cliffHeightCategory Context triple: [Freerider, cliffHeightCategory, over 900 meters]
-
A.
altitudeCategory
chosen
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
-
B.
hasCliffHeight
Indicates the relationship between a cliff and the measurement of its vertical height.
-
C.
hasCliff
Indicates that something possesses or features a steep, high rock face or abrupt vertical drop as part of its structure or environment.
-
D.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
E.
parentPeakOrCliff
Indicates that one peak or cliff is the higher-level or containing landform relative to another, typically representing a subordinate-to-parent topographic relationship.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0f43b08190a5abd936b14603b7 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.