Triple

T17735666
Position Surface form Disambiguated ID Type / Status
Subject Kakita River E442707 entity
Predicate recreationRestriction P18323 FINISHED
Object limited access to protect clarity and ecosystem 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: limited access to protect clarity and ecosystem | Statement: [Kakita River, recreationRestriction, limited access to protect clarity and ecosystem]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recreationRestriction
Context triple: [Kakita River, recreationRestriction, limited access to protect clarity and ecosystem]
  • A. recreationRegulation chosen
    Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
  • B. withinRecreationArea
    Indicates that one entity is located inside the spatial bounds of a designated recreation area associated with another entity.
  • C. hasRecreationConstraint
    Indicates a restriction or limitation placed on how recreation or leisure activities may occur or be used.
  • D. recreationUseLevel
    Indicates the intensity or degree to which an entity is used for recreational activities.
  • E. activitiesRestricted
    Indicates that certain actions or behaviors are limited, prohibited, or constrained under specified conditions or for particular entities.
  • 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e478eaff6c81909c7bd438b8c6c987 completed April 19, 2026, 6:40 a.m.
PD Predicate disambiguation batch_69e3cde815e08190881972e2d80d151e completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 10:08 a.m.