Triple

T22968888
Position Surface form Disambiguated ID Type / Status
Subject Chiwei Yu E571123 entity
Predicate hasSurroundingWatersStatus P150438 FINISHED
Object disputed exclusive economic zones 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: disputed exclusive economic zones | Statement: [Chiwei Yu, hasSurroundingWatersStatus, disputed exclusive economic zones]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSurroundingWatersStatus
Context triple: [Chiwei Yu, hasSurroundingWatersStatus, disputed exclusive economic zones]
  • A. hasSurroundingWaters
    Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
  • B. hasNearbyWater
    Indicates that one entity is located close to a body of water associated with or relevant to another entity.
  • C. hasBodyOfWaterType
    Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
  • D. hasNearbyWatersUsedBy
    Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
  • E. hasShelteredWaters
    Indicates that one location provides protected or calm waters for another location or activity, shielding it from rough or open conditions.
  • 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_69e245b2c6548190a0e4c7f2f7df2d48 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18231459881909dd25a0630c494d8 completed April 29, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69ef3b9101f48190a06c69dff26c6441 completed April 27, 2026, 10:33 a.m.
PDg Predicate description generation batch_69ef538a115081908982597f79355840 completed April 27, 2026, 12:16 p.m.
Created at: April 17, 2026, 3:48 p.m.