Triple
T4449408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truckee River Whitewater Park |
E96369
|
entity |
| Predicate | hasPublicAccessPoints |
P30373
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Truckee River Whitewater Park, hasPublicAccessPoints, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicAccessPoints Context triple: [Truckee River Whitewater Park, hasPublicAccessPoints, multiple]
-
A.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
B.
isPubliclyAccessible
chosen
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
C.
hasPublicAddressSystem
Indicates that an entity is equipped with or includes a public address (PA) system for broadcasting audio announcements.
-
D.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
E.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d5975c8190bfe8a2d5d2dbf075 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.