Triple

T35616428
Position Surface form Disambiguated ID Type / Status
Subject Bogue Falaya River E1029179 entity
Predicate hasRecreationalUseLevel P85481 FINISHED
Object popular local paddling destination 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: popular local paddling destination | Statement: [Bogue Falaya River, hasRecreationalUseLevel, popular local paddling destination]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRecreationalUseLevel
Context triple: [Bogue Falaya River, hasRecreationalUseLevel, popular local paddling destination]
  • A. recreationUseLevel chosen
    Indicates the intensity or degree to which an entity is used for recreational activities.
  • B. hasRecreationalUseRestriction
    Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
  • C. hasRecreationalAspect
    Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
  • D. isRecreational
    Indicates that something is used or intended primarily for leisure, enjoyment, or non-work-related activities.
  • E. isRecreationalResourceFor
    Indicates that something serves as a facility, area, or service used by someone for leisure, recreation, or enjoyment.
  • 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_69f76e0709408190bbe322bf1707ef6b completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a04d8348190a4819666eab42c9b completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:05 p.m.