Triple

T8006098
Position Surface form Disambiguated ID Type / Status
Subject Premier League Playmaker of the Season E186366 entity
Predicate tieBreaking P6631 FINISHED
Object other performance criteria may be used if assists are equal 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: other performance criteria may be used if assists are equal | Statement: [Premier League Playmaker of the Season, tieBreaking, other performance criteria may be used if assists are equal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tieBreaking
Context triple: [Premier League Playmaker of the Season, tieBreaking, other performance criteria may be used if assists are equal]
  • A. tiebreaker chosen
    Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
  • B. breaksWith
    Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
  • C. maintainsTieWith
    Indicates that one entity keeps an ongoing connection or relationship with another entity over time.
  • D. tiebreakerGameLoser
    Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
  • E. associatedBreak
    Indicates a relationship where one entity is linked to a specific break, interruption, or pause that is relevant to its state, schedule, or operation.
  • 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_69ca82aaaf24819084b94d18f699ba53 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3cf72fc08190aa78b97c1ab92f90 completed March 31, 2026, 3:18 a.m.
PD Predicate disambiguation batch_69cb048c9f488190b4fb8917a9c21bc5 completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:18 p.m.