Triple

T33963239
Position Surface form Disambiguated ID Type / Status
Subject Wilson Kipketer E870776 entity
Predicate hasCompetitorInEvent P205264 FINISHED
Object 800 metres runners 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: 800 metres runners | Statement: [Wilson Kipketer, hasCompetitorInEvent, 800 metres runners]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCompetitorInEvent
Context triple: [Wilson Kipketer, hasCompetitorInEvent, 800 metres runners]
  • A. hasCompetitionElement
    Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
  • B. hasCompetitorNumber
    Indicates that an entity is associated with a specific competitor identification number used to distinguish it in a competitive context.
  • C. hasCompetition
    Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
  • D. tieneCompetenciaEn
    Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
  • E. supportsCompetitionParticipationOf
    Indicates that one entity provides assistance, resources, or endorsement enabling another entity to take part in a competition.
  • 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_69f3499ce8e88190b66e1d49ad8c7037 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379f963908190846d232f386fd98f completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c80ba448190853011097a151b7e completed May 12, 2026, 7:16 p.m.
Created at: May 1, 2026, 1:50 a.m.