Triple

T5841002
Position Surface form Disambiguated ID Type / Status
Subject ASEAN member state E129592 entity
Predicate sharesPrinciple P66652 FINISHED
Object respect for sovereignty and territorial integrity 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: respect for sovereignty and territorial integrity | Statement: [ASEAN member state, sharesPrinciple, respect for sovereignty and territorial integrity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesPrinciple
Context triple: [ASEAN member state, sharesPrinciple, respect for sovereignty and territorial integrity]
  • A. sharesUniverseWith
    Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
  • B. sharesIn
    Indicates that one entity holds or possesses shares or ownership stakes in another entity.
  • C. sharesPowerWith
    Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
  • D. share
    Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
  • E. sharesBaseWith
    Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
  • 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_69c0084bd31c8190a796bb6284845e83 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03c9239e08190bff7ef2bd6d21ae0 completed March 22, 2026, 7:01 p.m.
PD Predicate disambiguation batch_69c0334412388190bc594794ec5754f9 completed March 22, 2026, 6:21 p.m.
PDg Predicate description generation batch_69c03c8d579081909d7b97fc9014b5d7 completed March 22, 2026, 7:01 p.m.
Created at: March 22, 2026, 3:54 p.m.