Triple

T14337512
Position Surface form Disambiguated ID Type / Status
Subject Russian Federation baselines E355501 entity
Predicate definesOuterLimitOf P49302 FINISHED
Object Russian territorial sea breadth 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: Russian territorial sea breadth | Statement: [Russian Federation baselines, definesOuterLimitOf, Russian territorial sea breadth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesOuterLimitOf
Context triple: [Russian Federation baselines, definesOuterLimitOf, Russian territorial sea breadth]
  • A. outerLimitDefinedFrom chosen
    Indicates that the outer boundary or maximum extent of one entity is determined or specified based on another entity.
  • B. definesLimitOf
    Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
  • C. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • D. definesMaximum
    Indicates that one entity specifies or sets the upper limit or greatest allowable value for another entity.
  • E. typeOfLimit
    Indicates that one entity specifies the category or kind of limit that applies 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_69d8278fa2108190bc0d0e7939c1eb03 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8c2241e48190a0c626b3d741966a completed April 14, 2026, 6:49 p.m.
PD Predicate disambiguation batch_69de2a9958e881909d03ac03f135163e completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:14 a.m.