Triple

T18874998
Position Surface form Disambiguated ID Type / Status
Subject ONUC E461658 entity
Predicate usedForceUnder P133293 FINISHED
Object UN Security Council authorization 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: UN Security Council authorization | Statement: [ONUC, usedForceUnder, UN Security Council authorization]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedForceUnder
Context triple: [ONUC, usedForceUnder, UN Security Council authorization]
  • A. usesForces
    Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
  • B. inForceWith
    Indicates that a rule, condition, or agreement is currently active and being applied in conjunction with a specified entity or set of entities.
  • C. associatedForce
    Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
  • D. usedAgainst
    Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
  • E. hasForceStrength
    Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c3cd49748190948d535918aec3de completed April 20, 2026, 6:12 a.m.
PD Predicate disambiguation batch_69e48d22dde8819093b1d963bd673365 completed April 19, 2026, 8:06 a.m.
PDg Predicate description generation batch_69e49785fd7081909577e90a55df0a35 completed April 19, 2026, 8:51 a.m.
Created at: April 10, 2026, 11:57 a.m.