Triple
T27293962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogan Ridge Trail |
E688705
|
entity |
| Predicate | typicalDifficulty |
P200716
|
FINISHED |
| Object | moderate to rugged |
—
|
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 to rugged | Statement: [Mogan Ridge Trail, typicalDifficulty, moderate to rugged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDifficulty Context triple: [Mogan Ridge Trail, typicalDifficulty, moderate to rugged]
-
A.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
B.
typicalIntermediateLevel
Indicates that something represents a common or standard degree of difficulty, complexity, or proficiency that falls between beginner and advanced levels.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalDynamicLevel
Indicates the usual or characteristic intensity or volume level at which an action, event, or interaction typically occurs.
-
E.
typicalSnowDifficulty
Indicates the usual or characteristic level of difficulty associated with snow conditions for an activity, route, or location.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
| PDg | Predicate description generation | batch_69ffa96638108190942dcfbe0516c37a |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 27, 2026, 11:17 a.m.