Triple

T6611365
Position Surface form Disambiguated ID Type / Status
Subject The Penalty Kick E149244 entity
Predicate ballInPlayCondition P25453 FINISHED
Object ball is in play when it is kicked and clearly moves 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: ball is in play when it is kicked and clearly moves | Statement: [The Penalty Kick, ballInPlayCondition, ball is in play when it is kicked and clearly moves]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ballInPlayCondition
Context triple: [The Penalty Kick, ballInPlayCondition, ball is in play when it is kicked and clearly moves]
  • A. ballCondition chosen
    Indicates the specific state or status a ball is in, such as its physical condition, readiness for use, or compliance with required standards.
  • B. checkBallRule
    Indicates that an agent verifies whether a ball-related condition or rule is satisfied in a given context.
  • C. playsOnSideOfBall
    Indicates that one entity participates in a game or sport on a particular side or unit of the ball (e.g., offense or defense).
  • D. matchBall
    Indicates that an entity is associated with or participates in a particular ball used in a match or game.
  • E. sideOfBall
    Indicates the relative position of an entity with respect to a ball, specifying on which side of the ball the entity is located.
  • 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_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.
Created at: March 27, 2026, 1:57 p.m.