Triple
T35063126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Wells Valley Wilderness |
E1011650
|
entity |
| Predicate | recreationOpportunity |
P182069
|
FINISHED |
| Object | solitude |
—
|
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: solitude | Statement: [Indian Wells Valley Wilderness, recreationOpportunity, solitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationOpportunity Context triple: [Indian Wells Valley Wilderness, recreationOpportunity, solitude]
-
A.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
B.
isOutdoorRecreationSite
Indicates that a place is designated or used primarily for recreational activities that take place outdoors.
-
C.
recreationAccessPoint
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
D.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
E.
isRecreationalResourceFor
Indicates that something serves as a facility, area, or service used by someone for leisure, recreation, or enjoyment.
- F. None of above. chosen
Provenance (4 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.