Triple

T33937939
Position Surface form Disambiguated ID Type / Status
Subject Seminoe Reservoir E870084 entity
Predicate recreationalUseManagedBy P79731 FINISHED
Object Wyoming State Parks NE NERFINISHED

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: Wyoming State Parks | Statement: [Seminoe Reservoir, recreationalUseManagedBy, Wyoming State Parks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recreationalUseManagedBy
Context triple: [Seminoe Reservoir, recreationalUseManagedBy, Wyoming State Parks]
  • A. hasRecreationalManagement
    Indicates that an entity is responsible for overseeing, organizing, or providing recreational activities, facilities, or services for another entity or area.
  • B. hasRecreationalUseRestriction
    Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
  • C. recreationUseLevel
    Indicates the intensity or degree to which an entity is used for recreational activities.
  • D. isRecreationalResourceFor
    Indicates that something serves as a facility, area, or service used by someone for leisure, recreation, or enjoyment.
  • E. operatorOfRecreationArea chosen
    Indicates that an entity is responsible for managing, running, or overseeing the operations of a recreation area.
  • 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_69f3499a59788190bff762a891471b31 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7064e906881909c3186c646145d34 completed May 3, 2026, 8:24 a.m.
PD Predicate disambiguation batch_69f70100ec1c8190a6b97f50e88891f2 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:49 a.m.