Triple

T21703677
Position Surface form Disambiguated ID Type / Status
Subject UEFA Euro 1968 matches E535718 entity
Predicate usesMatchDuration P99634 FINISHED
Object 90 minutes regular time 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: 90 minutes regular time | Statement: [UEFA Euro 1968 matches, usesMatchDuration, 90 minutes regular time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesMatchDuration
Context triple: [UEFA Euro 1968 matches, usesMatchDuration, 90 minutes regular time]
  • A. usesMatchLength chosen
    Indicates that one entity applies or enforces the same length or duration as that of a corresponding match or matching element.
  • B. usesMatchesFrom
    Indicates that one entity relies on or incorporates matches (e.g., pattern matches, rule matches, or result matches) produced by another entity or process.
  • C. hasTypicalPerformanceDuration
    Indicates the usual or expected length of time that a performance or activity typically lasts.
  • D. usesTimingRules
    Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
  • E. possibleDuration
    Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
  • 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_69e0c46b44c0819088ab883ebd44e0e8 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef9b82901c81909de242c920fbc164 completed April 27, 2026, 5:23 p.m.
PD Predicate disambiguation batch_69e6969113cc8190ab69855ef5667e4b completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:46 p.m.