Triple

T26381340
Position Surface form Disambiguated ID Type / Status
Subject Spooner’s Cove E663133 entity
Predicate recreationalRestrictions P144020 FINISHED
Object fires restricted or prohibited 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: fires restricted or prohibited | Statement: [Spooner’s Cove, recreationalRestrictions, fires restricted or prohibited]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recreationalRestrictions
Context triple: [Spooner’s Cove, recreationalRestrictions, fires restricted or prohibited]
  • A. hasRecreationalUseRestriction chosen
    Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
  • B. recreationRegulation
    Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
  • C. withinRecreationArea
    Indicates that one entity is located inside the spatial bounds of a designated recreation area associated with another entity.
  • D. wildernessActRestrictions
    Indicates that certain activities or uses are limited or prohibited in an area due to regulations established by the Wilderness Act.
  • E. recreationUseLevel
    Indicates the intensity or degree to which an entity is used for recreational 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_69ee88374adc81909868f3bab374a32f completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f61f12b0f08190bc4a16907941864c completed May 2, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69f61b3a8ae0819090189fbd8eb19f2f completed May 2, 2026, 3:41 p.m.
Created at: April 26, 2026, 11:18 p.m.