Triple

T2625586
Position Surface form Disambiguated ID Type / Status
Subject EFL League Two E59109 entity
Predicate usesPromotionPlayOffs P18796 FINISHED
Object true 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: true | Statement: [EFL League Two, usesPromotionPlayOffs, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesPromotionPlayOffs
Context triple: [EFL League Two, usesPromotionPlayOffs, true]
  • A. hasPlayOffs chosen
    Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
  • B. hasRelegationPlayOff
    Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
  • C. hasPromotionRelegation
    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.
  • D. playoffQualification
    Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
  • E. usesPlayoffs
    Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
  • 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_69ab4ac558388190962492cd2e1b0ce6 completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abdb0e7b888190bfa5d2e33f00ec0f completed March 7, 2026, 8 a.m.
PD Predicate disambiguation batch_69abd810d7f481908e81c305772c4c14 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:50 p.m.