Triple

T27381510
Position Surface form Disambiguated ID Type / Status
Subject Kiser Lake State Park E691242 entity
Predicate hasProhibition P38719 FINISHED
Object no motorized boats on Kiser Lake 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 motorized boats on Kiser Lake | Statement: [Kiser Lake State Park, hasProhibition, no motorized boats on Kiser Lake]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProhibition
Context triple: [Kiser Lake State Park, hasProhibition, no motorized boats on Kiser Lake]
  • A. isProhibitedFor chosen
    Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
  • B. isOftenProhibitedAt
    Indicates that something is frequently not allowed or banned in a particular place, context, or situation.
  • C. prohibits
    Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
  • D. isBarred
    Indicates that an entity is officially prohibited or excluded from participating in, entering, or accessing another entity or activity.
  • E. hadRestrictionsOn
    Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
  • 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_69ef52022538819081f873d0c84a6dd6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69fddd373cdc8190be1b12e70e4deb1f completed May 8, 2026, 12:55 p.m.
PD Predicate disambiguation batch_69fddc6915a88190ad41e379aa3ede13 completed May 8, 2026, 12:51 p.m.
Created at: April 27, 2026, 12:22 p.m.