Triple

T28004949
Position Surface form Disambiguated ID Type / Status
Subject Premier League managers E707250 entity
Predicate employmentContract P11918 FINISHED
Object fixed-term contract 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: fixed-term contract | Statement: [Premier League managers, employmentContract, fixed-term contract]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: employmentContract
Context triple: [Premier League managers, employmentContract, fixed-term contract]
  • A. employmentType chosen
    Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
  • B. employment
    Indicates a relationship where one entity hires, contracts, or otherwise engages another to perform work or services, typically in exchange for compensation.
  • C. employmentAction
    Indicates an action or event that changes, initiates, or terminates an employment relationship between entities.
  • D. contractStatus
    Indicates the current state or phase of a contract within its lifecycle (e.g., draft, active, suspended, or terminated).
  • E. commonEmployment
    Indicates that two or more entities share the same employer or have worked for the same organization.
  • 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_69ef96ba350c81908230d0b501b974c4 completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f6978fe97081908fe568091ad9b159 completed May 3, 2026, 12:32 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
Created at: April 27, 2026, 7:59 p.m.