Triple

T5528611
Position Surface form Disambiguated ID Type / Status
Subject Premier League under-21 team E144988 entity
Predicate ageRuleFlexibility P39362 FINISHED
Object limited over-age exemptions 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: limited over-age exemptions | Statement: [Premier League under-21 team, ageRuleFlexibility, limited over-age exemptions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ageRuleFlexibility
Context triple: [Premier League under-21 team, ageRuleFlexibility, limited over-age exemptions]
  • A. agePolicy chosen
    Indicates a rule or restriction that specifies how something should be treated or allowed based on the ages of the entities involved.
  • B. ageLimitAppliesAt
    Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
  • C. ageStatus
    Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
  • D. ageSetting
    Indicates that one entity specifies, adjusts, or defines the age value or age-related parameter of another entity.
  • E. ageRange
    Indicates the span of ages within which an entity or relationship is considered valid or applicable.
  • 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_69c008f9955881909bfa8348b56b4739 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f8b6c348190b7d414dc1907d09a completed March 22, 2026, 4:57 p.m.
PD Predicate disambiguation batch_69c01b0a06348190b39ac9fe80d2836a completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:34 p.m.