Triple

T24691047
Position Surface form Disambiguated ID Type / Status
Subject 2025 UEFA Champions League Final E611437 entity
Predicate hasRegulationTimeDuration P25687 FINISHED
Object 90 minutes 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 | Statement: [2025 UEFA Champions League Final, hasRegulationTimeDuration, 90 minutes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegulationTimeDuration
Context triple: [2025 UEFA Champions League Final, hasRegulationTimeDuration, 90 minutes]
  • A. regulatesTimeFor
    Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
  • B. hasOfficialDuration
    Indicates the formally defined length of time associated with an event, process, or entity.
  • C. regulationMinutes chosen
    Indicates the number of minutes played during the standard regulation period of a game, excluding any overtime or extra periods.
  • D. hasDurationType
    Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
  • E. hasDurationCharacteristic
    Indicates that something possesses a specific temporal property, such as length, span, or persistence over time.
  • 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_69e2c4d678b081908910f4271627a31a completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f5f6baf2d48190a6a4cd6501be87d2 completed May 2, 2026, 1:06 p.m.
PD Predicate disambiguation batch_69f5afd5baac8190bb8ed576813c8591 completed May 2, 2026, 8:03 a.m.
Created at: April 18, 2026, 3:20 a.m.