Triple

T1343964
Position Surface form Disambiguated ID Type / Status
Subject Antarctic Treaty E28527 entity
Predicate definesRegionAs P27400 FINISHED
Object all land and ice shelves south of 60°S latitude 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: all land and ice shelves south of 60°S latitude | Statement: [Antarctic Treaty, definesRegionAs, all land and ice shelves south of 60°S latitude]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesRegionAs
Context triple: [Antarctic Treaty, definesRegionAs, all land and ice shelves south of 60°S latitude]
  • A. formationRegion
    Indicates the place or area where something originates, is created, or comes into being.
  • B. coreRegionOf
    Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
  • C. regionRuled
    Indicates that a particular region is governed or controlled by a specified ruler or authority.
  • D. regionException
    Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
  • E. regionNamedAfter
    Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
  • F. None of above. chosen

Provenance (4 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_69a49854eb3481908c7d56b2e449a290 completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c23b8a9081908b78405d4ef806af completed March 1, 2026, 10:48 p.m.
PD Predicate disambiguation batch_69a4bef3e8fc8190ac9a1ba9b5879483 completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4c06721488190ac7f6e012f21af3d completed March 1, 2026, 10:40 p.m.
Created at: March 1, 2026, 7:56 p.m.