Triple

T14240464
Position Surface form Disambiguated ID Type / Status
Subject United Nations Intelligence Taskforce E352988 entity
Predicate laterNameChangeReason P2136 FINISHED
Object licensing issues with the real United Nations 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: licensing issues with the real United Nations | Statement: [United Nations Intelligence Taskforce, laterNameChangeReason, licensing issues with the real United Nations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laterNameChangeReason
Context triple: [United Nations Intelligence Taskforce, laterNameChangeReason, licensing issues with the real United Nations]
  • A. nameChangeReason chosen
    Indicates the reason or justification for a change in an entity’s name.
  • B. changedSurnameFrom
    Indicates that an entity has adopted a new surname that was previously a different, specified surname.
  • C. changedSurnameTo
    Indicates that an entity has adopted a new surname, replacing their previous one, with the new surname specified as the related entity.
  • D. changedNameOn
    Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
  • E. underwentNameChangeTo
    Indicates that an entity previously known by one name has changed its name to the specified new name.
  • 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_69d8278adc7c8190a9218d69bce3c4e6 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de62432fb48190b153805b85c4f2d2 completed April 14, 2026, 3:50 p.m.
PD Predicate disambiguation batch_69de05bf069c8190b69f00f00f5eb126 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:08 a.m.