Triple

T13558334
Position Surface form Disambiguated ID Type / Status
Subject Sansha City E323837 entity
Predicate maritimeClaimBasis P110351 FINISHED
Object Chinese claims in the South China Sea 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: Chinese claims in the South China Sea | Statement: [Sansha City, maritimeClaimBasis, Chinese claims in the South China Sea]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritimeClaimBasis
Context triple: [Sansha City, maritimeClaimBasis, Chinese claims in the South China Sea]
  • A. maritimeClaimType
    Indicates the specific nature or category of a party’s asserted rights or jurisdiction over a maritime area.
  • B. shipInvolved
    Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
  • C. shareMaritimeAgreements
    Indicates that two or more entities are parties to the same maritime-related agreements, such as treaties, conventions, or cooperative arrangements governing activities at sea.
  • D. maritimeHazard
    Indicates a condition, object, or situation at sea that poses a risk to vessels, navigation, or maritime operations.
  • E. maritimeVariant
    Indicates a version or form of something that is specifically adapted for or used in maritime (sea-related) contexts.
  • 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbb9ee3f081909056dc1a92c40b7a completed April 12, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69dbae13bec4819084c1770638c00ed9 completed April 12, 2026, 2:37 p.m.
PDg Predicate description generation batch_69dbbb8c77dc8190b7bd803b5e168d23 completed April 12, 2026, 3:34 p.m.
Created at: April 9, 2026, 9:47 p.m.