Triple

T15643204
Position Surface form Disambiguated ID Type / Status
Subject Taiping Island E376114 entity
Predicate hasLegalStatusDispute P23974 FINISHED
Object classification as island or rock under UNCLOS 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: classification as island or rock under UNCLOS | Statement: [Taiping Island, hasLegalStatusDispute, classification as island or rock under UNCLOS]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegalStatusDispute
Context triple: [Taiping Island, hasLegalStatusDispute, classification as island or rock under UNCLOS]
  • A. hasDisputedStatus chosen
    Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
  • B. hasDisputedStatusWith
    Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
  • C. hasLegalIssue
    Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
  • D. hasLegalProceeding
    Indicates that there is a formal legal action, case, or proceeding involving the related entities.
  • E. hasLegalStatus
    Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
  • 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_69d85cd035a48190b73d5579ab73969a completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed23d688190bea996f90989d406 completed April 16, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69deda890140819082608931e993dd61 completed April 15, 2026, 12:23 a.m.
Created at: April 10, 2026, 4:15 a.m.