Triple

T33454275
Position Surface form Disambiguated ID Type / Status
Subject Gamma Ethniki E856727 entity
Predicate determinesRelegationBy P7593 FINISHED
Object final league standings 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: final league standings | Statement: [Gamma Ethniki, determinesRelegationBy, final league standings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: determinesRelegationBy
Context triple: [Gamma Ethniki, determinesRelegationBy, final league standings]
  • A. hasRelegationTo
    Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
  • B. determinedBy chosen
    Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
  • C. hasRelegationHistory
    Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
  • D. canBeReassignedBy
    Indicates that one entity has the authority or ability to change or transfer another entity’s assignment or allocation.
  • E. determinesRepresentativeFor
    Indicates that one entity selects or designates another entity to act as its representative in a given context.
  • 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_69f3497281a08190b4705de0b5f26ba7 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fb19063c81909466b329655c8583 completed May 3, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f6f96badb08190994442c2aba840b1 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:37 a.m.