Triple

T22690853
Position Surface form Disambiguated ID Type / Status
Subject Video Assistant Referee system E561045 entity
Predicate appliesToDecisionType P2165 FINISHED
Object goal or no goal 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: goal or no goal | Statement: [Video Assistant Referee system, appliesToDecisionType, goal or no goal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesToDecisionType
Context triple: [Video Assistant Referee system, appliesToDecisionType, goal or no goal]
  • A. usesDecisionBoundaryType
    Indicates that one entity applies or relies on a specific type of decision boundary in making classifications or decisions.
  • B. associatedWithDecision
    Indicates a relationship where an entity is linked or connected to a particular decision, such that the decision is relevant to, influenced by, or otherwise tied to that entity.
  • C. includesDecisionOn
    Indicates that one item or process contains, encompasses, or explicitly addresses a particular decision or determination.
  • D. decisionType chosen
    Indicates the specific category or nature of a decision associated with an entity or event.
  • E. appliesTo
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • 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_69e2454d71b48190a1f80af9f82b6fcf completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1789adcc48190b4a717166d5dba19 completed April 29, 2026, 3:18 a.m.
PD Predicate disambiguation batch_69ee62b2259c819091ed1387a748b9f3 completed April 26, 2026, 7:08 p.m.
Created at: April 17, 2026, 3:13 p.m.