Triple

T35666913
Position Surface form Disambiguated ID Type / Status
Subject Brantley Lake E1030591 entity
Predicate isContainedInProtectedArea P10759 FINISHED
Object Brantley Lake State Park 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: Brantley Lake State Park | Statement: [Brantley Lake, isContainedInProtectedArea, Brantley Lake State Park]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isContainedInProtectedArea
Context triple: [Brantley Lake, isContainedInProtectedArea, Brantley Lake State Park]
  • A. isInProtectedArea chosen
    Indicates that an entity is located within a designated protected or conservation area.
  • B. isProtectedAreaOf
    Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
  • C. isInProtectedAreaVicinity
    Indicates that an entity is located close to, but not necessarily within, a designated protected area.
  • D. hasProtectedArea
    Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
  • E. isProtectedAreaBufferFor
    Indicates that one area functions as a designated buffer zone surrounding and protecting another protected 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_69f76e09f87881909c954aaac176c34f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7bbf906d8819099020e548dd56bc9 completed May 3, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69f7b9a2dcf88190a7c9e109e41267be completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:05 p.m.