Triple

T1948919
Position Surface form Disambiguated ID Type / Status
Subject CMC Chairman E42115 entity
Predicate isTypicallySelectedBy P381 FINISHED
Object top party leadership 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: top party leadership | Statement: [CMC Chairman, isTypicallySelectedBy, top party leadership]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTypicallySelectedBy
Context triple: [CMC Chairman, isTypicallySelectedBy, top party leadership]
  • A. isSelective
    Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
  • B. typicalNumberOfSelections
    Indicates the usual or expected count of selections made in a given choice or selection process.
  • C. selectedTo
    Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
  • D. selectionMadeBy chosen
    Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
  • E. holderSelection
    Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
  • 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb3315df481908f60cd87453fbc03 completed March 7, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69abaff25a588190bb4cbc8df9fc6d64 completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:36 p.m.