Triple

T9545583
Position Surface form Disambiguated ID Type / Status
Subject Brecon E230273 entity
Predicate locatedInNationalParkArea P9791 FINISHED
Object Brecon Beacons National Park fringe 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: Brecon Beacons National Park fringe | Statement: [Brecon, locatedInNationalParkArea, Brecon Beacons National Park fringe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInNationalParkArea
Context triple: [Brecon, locatedInNationalParkArea, Brecon Beacons National Park fringe]
  • A. withinNationalPark chosen
    Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
  • B. locatedInNationalLakeshore
    Indicates that one place or feature is situated within the boundaries of a designated national lakeshore area.
  • C. locatedInNationalCharacterArea
    Indicates that one entity is geographically situated within the boundaries of a specified national character area.
  • D. situatedInProtectedArea
    Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
  • E. isWithinPark
    Indicates that one entity is located inside the boundaries of a park that contains it.
  • 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_69ca847c70b8819088a0a0bad64a50d6 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9901f2bc8190a4076f5947660df9 completed April 1, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69ccd58bd21881908b860e3ee469af13 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:01 p.m.