Triple
T14963936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tia Falls |
E373136
|
entity |
| Predicate | hasWalkingTrackGrade |
P24163
|
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: [Tia Falls, hasWalkingTrackGrade, easy to moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingTrackGrade Context triple: [Tia Falls, hasWalkingTrackGrade, easy to moderate]
-
A.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
C.
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.
-
D.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
E.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6d0487c8190b7754af8c5014b37 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.