Triple

T6836960
Position Surface form Disambiguated ID Type / Status
Subject Serie B E157473 entity
Predicate usesRelegationPlayouts P31084 FINISHED
Object sometimes, depending on rules of season 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: sometimes, depending on rules of season | Statement: [Serie B, usesRelegationPlayouts, sometimes, depending on rules of season]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesRelegationPlayouts
Context triple: [Serie B, usesRelegationPlayouts, sometimes, depending on rules of season]
  • A. hasRelegationTo
    Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
  • B. playedPublicRole
    Indicates that an entity has performed a notable, visible function or position in the public sphere, such as in government, media, or community leadership.
  • C. hasRelegationPlayOff chosen
    Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
  • D. supportsRemotePlay
    Indicates that one entity enables or is compatible with remote play functionality for another entity.
  • E. hasRelegationHistory
    Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
  • 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_69c6882c53608190b99aebef079b23bd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d67c1c508190ab39b8aaaaacc628 completed March 27, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69c6d09f90648190bc0a462c7d59de1b completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:19 p.m.