Triple

T34747234
Position Surface form Disambiguated ID Type / Status
Subject Metolius, Oregon E1001669 entity
Predicate nearbyOutdoorRecreationArea P68166 FINISHED
Object Deschutes National Forest 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: Deschutes National Forest | Statement: [Metolius, Oregon, nearbyOutdoorRecreationArea, Deschutes National Forest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyOutdoorRecreationArea
Context triple: [Metolius, Oregon, nearbyOutdoorRecreationArea, Deschutes National Forest]
  • A. hasRecreationalActivityNearby
    Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
  • B. nearbyCampground
    Indicates that one location has a campground situated close to it in geographic proximity.
  • C. nearbyActivityHub
    Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
  • D. nearbyResortArea
    Indicates that a resort area is located close to or within a short distance of a specified place or entity.
  • E. hasRecreationalUseNearby chosen
    Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
  • 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_69f76db0367081909b57c50a7fb03025 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fe86cad5108190b0164b8bc6fc23ea completed May 9, 2026, 12:58 a.m.
PD Predicate disambiguation batch_69fe83c0c9888190b6fc40c7f727b569 completed May 9, 2026, 12:45 a.m.
Created at: May 3, 2026, 3:59 p.m.