Triple

T10176821
Position Surface form Disambiguated ID Type / Status
Subject United Nations forces E235874 entity
Predicate canBeMandatedUnder P54028 FINISHED
Object Chapter VI of the UN Charter 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: Chapter VI of the UN Charter | Statement: [United Nations forces, canBeMandatedUnder, Chapter VI of the UN Charter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeMandatedUnder
Context triple: [United Nations forces, canBeMandatedUnder, Chapter VI of the UN Charter]
  • A. canMandate
    Indicates that one entity has the authority or power to require another entity to perform or comply with something.
  • B. hasUNMandateType chosen
    Indicates the specific type or category of United Nations mandate under which an action, mission, or operation is authorized or conducted.
  • C. hasMandate
    Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
  • D. mandateRestriction
    Indicates that an authority imposes a binding limitation or requirement on an entity’s actions or conditions.
  • E. isMandatoryInSomeJurisdictions
    Indicates that the subject is legally required or compulsory in at least one jurisdiction or legal authority.
  • 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_69ca84d1d5f88190ab878a1021ecff68 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdecd4e3188190aa5d9ee95595f4a7 completed April 2, 2026, 4:13 a.m.
PD Predicate disambiguation batch_69cd7c79f21c8190a7f31b2eab80b8ba completed April 1, 2026, 8:13 p.m.
Created at: March 30, 2026, 9:11 p.m.