Triple
T32765855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Creek Range Wilderness |
E837892
|
entity |
| Predicate | allowedRecreationActivity |
P75860
|
FINISHED |
| Object | hiking |
—
|
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: hiking | Statement: [Shell Creek Range Wilderness, allowedRecreationActivity, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedRecreationActivity Context triple: [Shell Creek Range Wilderness, allowedRecreationActivity, hiking]
-
A.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
B.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
-
C.
supportsRecreationAt
Indicates that one entity provides facilities, conditions, or resources that enable recreational activities to take place at a specified location.
-
D.
permittedActivity
chosen
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
E.
hasRecreationType
Indicates that an entity is associated with or offers a particular type or category of recreational activity.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:13 a.m.