Triple

T33356226
Position Surface form Disambiguated ID Type / Status
Subject NPC E854077 entity
Predicate includesPromotionRelegation P12779 FINISHED
Object yes 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: yes | Statement: [NPC, includesPromotionRelegation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesPromotionRelegation
Context triple: [NPC, includesPromotionRelegation, yes]
  • A. hasPromotionRelegation chosen
    Indicates that there is a system in which entities can move up (promotion) or down (relegation) between hierarchical levels based on defined criteria or performance.
  • B. hasPromotionRelegationRelationWith
    Indicates that there is a structured promotion and/or relegation linkage between two competitive levels or leagues, where teams can move up or down between them based on performance.
  • C. includesPromotionFrom
    Indicates that one entity contains or incorporates a promotion that originates from another entity.
  • D. allowsPromotionRelegationInternally
    Indicates that within a given system or organization, entities can move up or down between internal levels or tiers based on performance or criteria.
  • E. hasNoPromotionRelegation
    Indicates that there is no system of promotion to higher levels or relegation to lower levels within the relevant competitive structure.
  • 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_69f3496acbc8819099fd0305ecc42080 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a030f1480148190a5e8c8926ded252c completed May 12, 2026, 11:29 a.m.
PD Predicate disambiguation batch_6a030e7f5fa481909696733defefcc20 completed May 12, 2026, 11:26 a.m.
Created at: May 1, 2026, 1:34 a.m.