Triple
T28791762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fall Creek Unit |
E726972
|
entity |
| Predicate | typicalTrailDifficulty |
P196926
|
FINISHED |
| Object | easy to moderate |
—
|
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: easy to moderate | Statement: [Fall Creek Unit, typicalTrailDifficulty, easy to moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrailDifficulty Context triple: [Fall Creek Unit, typicalTrailDifficulty, easy to moderate]
-
A.
typicalTrailConditions
Indicates the usual or expected state of a trail’s surface and environment under normal conditions.
-
B.
typicalDifficulty
Indicates the usual or characteristic level of difficulty associated with performing an action or achieving a particular outcome.
-
C.
hasApproximateTrailDifficulty
chosen
Indicates that one entity is associated with another entity representing an estimated or non-exact level of trail difficulty.
-
D.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
E.
typicalSnowDifficulty
Indicates the usual or characteristic level of difficulty associated with snow conditions for an activity, route, or location.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
Created at: April 28, 2026, 6:23 a.m.