Triple
T24989788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Canyon Lake |
E625413
|
entity |
| Predicate | boatRestriction |
P144020
|
FINISHED |
| Object | no gas-powered motors |
—
|
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: no gas-powered motors | Statement: [Rose Canyon Lake, boatRestriction, no gas-powered motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRestriction Context triple: [Rose Canyon Lake, boatRestriction, no gas-powered motors]
-
A.
boatingAllowed
Indicates that operating or using boats is permitted in the specified area or context.
-
B.
hasRecreationalUseRestriction
chosen
Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
-
C.
accessRestrictedToShore
Indicates that access to something is limited exclusively to locations or entities situated on or near the shore.
-
D.
hasShorelineUseRestrictions
Indicates that there are specific rules or limitations governing how the shoreline area associated with an entity may be used or developed.
-
E.
hazardLevelForBoating
Indicates the degree of risk or danger that current conditions pose specifically for boating 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a4416e881909c58f3b4d9e4b42d |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:03 a.m.