Triple

T22838004
Position Surface form Disambiguated ID Type / Status
Subject Marine Nature Reserve E565997 entity
Predicate hasSpatialBoundary P126645 FINISHED
Object legally defined marine area 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: legally defined marine area | Statement: [Marine Nature Reserve, hasSpatialBoundary, legally defined marine area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpatialBoundary
Context triple: [Marine Nature Reserve, hasSpatialBoundary, legally defined marine area]
  • A. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • B. hasBoundaryShape
    Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
  • C. hasBoundaryUnit
    Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
  • D. hasDefinedBoundaries chosen
    Indicates that the entity possesses clearly established and recognized limits or borders that distinguish it from its surroundings or from other entities.
  • E. isPartOfLargerBoundary
    Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
  • 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_69e245869e188190a196584f36e682da completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e8244dc819089c0a7525fb512ab completed April 29, 2026, 3:44 a.m.
PD Predicate disambiguation batch_69eed2d117088190acbfe130d84f8627 completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:35 p.m.