Triple

T30974726
Position Surface form Disambiguated ID Type / Status
Subject Oregon and Idaho E789199 entity
Predicate shareProtectedArea P71293 FINISHED
Object Hells Canyon Wilderness 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: Hells Canyon Wilderness | Statement: [Oregon and Idaho, shareProtectedArea, Hells Canyon Wilderness]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareProtectedArea
Context triple: [Oregon and Idaho, shareProtectedArea, Hells Canyon Wilderness]
  • A. shareConservationArea chosen
    Indicates that two or more entities have a conservation area that overlaps or is jointly designated or managed.
  • B. hasProtectedArea
    Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
  • C. areaProtected
    Indicates that a specified geographic area is designated and managed as protected, typically restricting certain activities to conserve its natural or cultural resources.
  • D. protectsArea
    Indicates that one entity serves to guard, defend, or preserve a particular area or region from harm or intrusion.
  • E. protectedAreaAssociation
    Indicates an association where one entity is designated as, or linked to, a protected area in relation to another 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_69f224c4831c8190be53924ec25a150a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe96c2647c819082989f11e1ae3d35 completed May 9, 2026, 2:06 a.m.
PD Predicate disambiguation batch_69fe928615448190af939e5a94be55bb completed May 9, 2026, 1:48 a.m.
Created at: April 29, 2026, 8:55 p.m.