Triple

T18271294
Position Surface form Disambiguated ID Type / Status
Subject Premier League fixtures E437619 entity
Predicate constraints P22542 FINISHED
Object stadium availability 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: stadium availability | Statement: [Premier League fixtures, constraints, stadium availability]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: constraints
Context triple: [Premier League fixtures, constraints, stadium availability]
  • A. restriction
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • B. designedToConstrain
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • C. conditions chosen
    Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
  • D. constraintOption
    Indicates that one entity represents a specific selectable option or value that can be chosen to satisfy or configure a constraint imposed by another entity.
  • E. constructionConstraints
    Indicates that there are specific limitations, rules, or conditions governing how a construction or building activity may be carried out.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ff7e00548190a28916a696831336 completed April 19, 2026, 4:14 p.m.
PD Predicate disambiguation batch_69e44fd81c788190b08c6be3b07a08c5 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:34 a.m.