Triple
T35316036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Cross Trail |
E1019907
|
entity |
| Predicate | hasSteepness |
P77075
|
FINISHED |
| Object | moderately steep |
—
|
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: moderately steep | Statement: [White Cross Trail, hasSteepness, moderately steep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSteepness Context triple: [White Cross Trail, hasSteepness, moderately steep]
-
A.
hasSteepUpperSlopes
Indicates that the upper portions of an object or landform are characterized by relatively steep slopes or gradients.
-
B.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
C.
hasSlopeFeature
chosen
Indicates that an entity possesses or is characterized by a particular slope-related property or feature.
-
D.
hasSlopeRating
Indicates that something (typically a golf course or hole) is associated with a specific slope rating value that quantifies its relative difficulty for bogey golfers compared to scratch golfers.
-
E.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
Created at: May 3, 2026, 4:03 p.m.