Triple

T28541917
Position Surface form Disambiguated ID Type / Status
Subject Andrés Escobar E722311 entity
Predicate ownGoalMatch P25120 FINISHED
Object Colombia vs United States, 1994 FIFA World Cup group stage NE NERFINISHED

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: Colombia vs United States, 1994 FIFA World Cup group stage | Statement: [Andrés Escobar, ownGoalMatch, Colombia vs United States, 1994 FIFA World Cup group stage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ownGoalMatch
Context triple: [Andrés Escobar, ownGoalMatch, Colombia vs United States, 1994 FIFA World Cup group stage]
  • A. ownGoalBy chosen
    Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
  • B. officialGoal
    Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
  • C. ownGoalDirectlyAllowed
    Indicates that an own goal is permitted to be scored directly, without requiring any intervening touch or event.
  • D. ownGoalBeneficiaryTeam
    Indicates the team that gains the scoring benefit when an own goal is committed against it.
  • E. hasOppositionGoal
    Indicates that one entity’s goal is in direct conflict with, or aims to prevent the achievement of, another entity’s goal.
  • 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_69f01a5e42348190b1ffbca26e739c84 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f6500a3de08190920c56b104073e7f completed May 2, 2026, 7:27 p.m.
PD Predicate disambiguation batch_69f64cb0d8008190912e1430cfaf92aa completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 3:36 a.m.