Triple

T21761079
Position Surface form Disambiguated ID Type / Status
Subject Syrian exclusive economic zone E537163 entity
Predicate outerLimitType P38256 FINISHED
Object not to exceed 200 nautical miles 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: not to exceed 200 nautical miles | Statement: [Syrian exclusive economic zone, outerLimitType, not to exceed 200 nautical miles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: outerLimitType
Context triple: [Syrian exclusive economic zone, outerLimitType, not to exceed 200 nautical miles]
  • A. outerLimitDefinedFrom
    Indicates that the outer boundary or maximum extent of one entity is determined or specified based on another entity.
  • B. innerLimit
    Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
  • C. typeOfLimit chosen
    Indicates that one entity specifies the category or kind of limit that applies to another entity.
  • D. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • E. definesLimitOf
    Indicates that one entity specifies or establishes the maximum or boundary condition applicable 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_69e0c46f5d1c8190bf830409e98464e5 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01d91e9788190a11d0295306e78a4 completed April 28, 2026, 2:38 a.m.
PD Predicate disambiguation batch_69e6969e46088190b13d6e9025775ea3 completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:50 p.m.