Triple
T26191103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Peak Ridge |
E654964
|
entity |
| Predicate | hasRidgeDirection |
P100398
|
FINISHED |
| Object | generally east–west |
—
|
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: generally east–west | Statement: [Rocky Peak Ridge, hasRidgeDirection, generally east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRidgeDirection Context triple: [Rocky Peak Ridge, hasRidgeDirection, generally east–west]
-
A.
hasRidgeRoute
Indicates that one entity possesses or is associated with a route that follows or traverses a ridge.
-
B.
isRidge
Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
-
C.
hasSummitRidgeOrientation
chosen
Indicates the directional alignment or orientation of a summit ridge relative to cardinal or geographic directions.
-
D.
isOnRidgeBetween
Indicates that something is located on the ridge that lies between two other reference points or areas.
-
E.
hasRidges
Indicates that one entity possesses raised, linear or patterned ridges on its surface or structure in relation to another entity or context.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 8:44 p.m.