Triple
T6710993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weber Canyon |
E153138
|
entity |
| Predicate | stateProtectedAreaNearby |
P67111
|
FINISHED |
| Object | Weber River corridor recreation sites |
—
|
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: Weber River corridor recreation sites | Statement: [Weber Canyon, stateProtectedAreaNearby, Weber River corridor recreation sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateProtectedAreaNearby Context triple: [Weber Canyon, stateProtectedAreaNearby, Weber River corridor recreation sites]
-
A.
nearestMajorProtectedArea
Indicates the closest significant legally protected natural area to a given location or entity.
-
B.
nearbyProtectedSite
chosen
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
-
C.
hasNearbyNatureReserve
Indicates that one place or entity is located close to a designated nature reserve.
-
D.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
E.
isInProtectedAreaVicinity
Indicates that an entity is located close to, but not necessarily within, a designated protected area.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d121a92c8190a03f384a8aba84da |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.