Triple

T31713712
Position Surface form Disambiguated ID Type / Status
Subject France exclusive economic zone E809397 entity
Predicate maritimeZoneType P86884 FINISHED
Object EEZ 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: EEZ | Statement: [France exclusive economic zone, maritimeZoneType, EEZ]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritimeZoneType
Context triple: [France exclusive economic zone, maritimeZoneType, EEZ]
  • A. isPartOfMaritimeZone
    Indicates that one area or feature is contained within, or legally belongs to, a specified maritime zone.
  • B. isMaritimeRegion
    Indicates that a region is primarily associated with the sea or ocean, such as being coastal, oceanic, or otherwise defined by maritime characteristics or activities.
  • C. hasMaritimeZoneContext
    Indicates that the relationship or fact is specifically situated within, or qualified by, a particular maritime zone or maritime jurisdictional area.
  • D. seaAreaDesignation chosen
    Indicates the specific legal or administrative sea area classification that has been assigned to a given marine region.
  • E. marineRouteType
    Indicates the specific kind or classification of a maritime route used for travel, transport, or navigation between locations.
  • 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_69f348df4e048190a4a5a9932ada78d6 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6bbbef7a88190b0affdec1d41c1e0 completed May 3, 2026, 3:06 a.m.
PD Predicate disambiguation batch_69f6ba6cef208190bc5cd43d96127004 completed May 3, 2026, 3:01 a.m.
Created at: April 30, 2026, 11:16 p.m.