Triple

T6611370
Position Surface form Disambiguated ID Type / Status
Subject The Penalty Kick E149244 entity
Predicate goalkeeperPositionRequirement P72448 FINISHED
Object goalkeeper must be on the goal line facing the kicker 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: goalkeeper must be on the goal line facing the kicker | Statement: [The Penalty Kick, goalkeeperPositionRequirement, goalkeeper must be on the goal line facing the kicker]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: goalkeeperPositionRequirement
Context triple: [The Penalty Kick, goalkeeperPositionRequirement, goalkeeper must be on the goal line facing the kicker]
  • A. goaltender
    Indicates a relationship where an entity serves as the goalkeeper or primary defender of the goal for a team in a game or sport.
  • B. hasNumberOfGoaltenders
    Indicates the specific count of goaltenders associated with a given team, roster, or game context.
  • C. bestGoalkeeper
    Indicates that the subject is considered the top-performing or most skilled goalkeeper among a specified group or context.
  • D. losingGoaltender
    Indicates that a particular goaltender is the one who was in net for the team that lost the game.
  • E. goalHeight
    Indicates the target or desired height that something is intended or planned to reach.
  • F. None of above. chosen

Provenance (4 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_69c687ebc680819094caf71faba2efe2 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cf3796d08190a26e988386089447 completed March 27, 2026, 6:40 p.m.
PD Predicate disambiguation batch_69c6acfed25481909cac74c84a9fe088 completed March 27, 2026, 4:14 p.m.
PDg Predicate description generation batch_69c6cf3683d08190b19e2aad30f2800f completed March 27, 2026, 6:40 p.m.
Created at: March 27, 2026, 1:57 p.m.