Triple

T28073667
Position Surface form Disambiguated ID Type / Status
Subject 2014 Indian Premier League E709473 entity
Predicate reasonForUAEPhase P180220 FINISHED
Object 2014 Indian general election 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: 2014 Indian general election | Statement: [2014 Indian Premier League, reasonForUAEPhase, 2014 Indian general election]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForUAEPhase
Context triple: [2014 Indian Premier League, reasonForUAEPhase, 2014 Indian general election]
  • A. reasonForUse
    Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
  • B. reasonForGrant
    Indicates the justification, purpose, or cause for which a grant is awarded or provided.
  • C. reasonForConversion
    Indicates the cause, motivation, or justification behind a particular conversion event or change.
  • D. inUniverseReasonFor
    Indicates that one entity serves as the in-universe explanation or justification for the existence, behavior, or characteristics of another entity within a fictional setting.
  • E. statedReason
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • 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_69ef9b6f8078819098b741274cd1a2ee completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f739a638748190808e7a2930dce16e completed May 3, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69f732f2dc6c8190a4e86da98cc5eb05 completed May 3, 2026, 11:35 a.m.
PDg Predicate description generation batch_69f739a58b3c81908abc2b8738a65678 completed May 3, 2026, 12:03 p.m.
Created at: April 27, 2026, 8:47 p.m.