Triple
T21413242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fryman Canyon Loop Trail |
E528229
|
entity |
| Predicate | isUrbanAccessible |
P85349
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fryman Canyon Loop Trail, isUrbanAccessible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanAccessible Context triple: [Fryman Canyon Loop Trail, isUrbanAccessible, true]
-
A.
hasUrbanAccess
chosen
Indicates that an entity has access to urban areas, services, or infrastructure.
-
B.
isUrbanNode
Indicates that a location or entity functions as an urban center or node within a city or metropolitan network.
-
C.
isUrbanStreet
Indicates that a given street is located within an urban area or city environment rather than a rural or suburban setting.
-
D.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
E.
isUrbanService
Indicates that a service operates within or is specifically intended for an urban area or city environment.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b20017d8819096b1a679edc8943a |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:44 p.m.