Triple
T26217536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah State Route 143 |
E655670
|
entity |
| Predicate | recreationTypesSupported |
P3451
|
FINISHED |
| Object | camping access |
—
|
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: camping access | Statement: [Utah State Route 143, recreationTypesSupported, camping access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationTypesSupported Context triple: [Utah State Route 143, recreationTypesSupported, camping access]
-
A.
hasRecreationType
chosen
Indicates that an entity is associated with or offers a particular type or category of recreational activity.
-
B.
recreationSetting
Indicates the type of environment or context in which a recreational activity takes place.
-
C.
recreationUseLevel
Indicates the intensity or degree to which an entity is used for recreational activities.
-
D.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
E.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1b90a88190a77dcad664786c53 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:54 p.m.