Triple
T21790570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount LeConte Lodge area |
E537957
|
entity |
| Predicate | trailUseType |
P68232
|
FINISHED |
| Object | non-motorized trails only |
—
|
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: non-motorized trails only | Statement: [Mount LeConte Lodge area, trailUseType, non-motorized trails only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailUseType Context triple: [Mount LeConte Lodge area, trailUseType, non-motorized trails only]
-
A.
trailUsePolicy
chosen
Indicates the rules or guidelines governing how a trail may be accessed and used.
-
B.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
C.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
D.
rightOfWayUsedFor
Indicates that a particular right of way is utilized for a specific purpose, activity, or type of use.
-
E.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621f95cc8190a3e8619fbf29555a |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.