Triple

T30203133
Position Surface form Disambiguated ID Type / Status
Subject United Nations Security Council Resolution 1510 E767838 entity
Predicate expandedMandateBeyond P58867 FINISHED
Object Kabul NE NERFINISHED

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: Kabul | Statement: [United Nations Security Council Resolution 1510, expandedMandateBeyond, Kabul]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: expandedMandateBeyond
Context triple: [United Nations Security Council Resolution 1510, expandedMandateBeyond, Kabul]
  • A. mandateExpanded chosen
    Indicates that an entity’s scope of authority, responsibility, or mission has been broadened beyond its previous mandate.
  • B. mandateExpandedFor
    Indicates that an existing mandate has been broadened or extended in scope to apply to the specified entity or context.
  • C. expandedJurisdictionOf
    Indicates that an entity’s authority, control, or legal power has been extended to cover a broader scope, area, or set of subjects than it previously did.
  • D. mandateRestriction
    Indicates that an authority imposes a binding limitation or requirement on an entity’s actions or conditions.
  • E. extendsBeyond
    Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
  • 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_69f2247eb0848190b4032f302d39c0d9 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 29, 2026, 7:31 p.m.