Triple
T17376943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Siskiyou |
E422461
|
entity |
| Predicate | hasBoatRestriction |
P46319
|
FINISHED |
| Object | motorized and non-motorized boats allowed (local regulations apply) |
—
|
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: motorized and non-motorized boats allowed (local regulations apply) | Statement: [Lake Siskiyou, hasBoatRestriction, motorized and non-motorized boats allowed (local regulations apply)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoatRestriction Context triple: [Lake Siskiyou, hasBoatRestriction, motorized and non-motorized boats allowed (local regulations apply)]
-
A.
boatingAllowed
chosen
Indicates that operating or using boats is permitted in the specified area or context.
-
B.
hasBoatCapacity
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
C.
hasBoat
Indicates that one entity possesses, owns, or has control over a boat.
-
D.
hasBoatLine
Indicates that one entity operates, owns, or is associated with a particular boat service or boat route line.
-
E.
usesCrewedBoats
Indicates that an entity performs an activity or operation by employing boats that are crewed by people.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6ddbd081908908b953597977d2 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.