Triple

T32191044
Position Surface form Disambiguated ID Type / Status
Subject Miss Universe 1965 contestant E822249 entity
Predicate competedForTitle P69999 FINISHED
Object Miss Universe 1965 winner 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: Miss Universe 1965 winner | Statement: [Miss Universe 1965 contestant, competedForTitle, Miss Universe 1965 winner]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competedForTitle
Context triple: [Miss Universe 1965 contestant, competedForTitle, Miss Universe 1965 winner]
  • A. competedFor
    Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
  • B. challengedForTitleAgainst
    Indicates that one entity competed against another in a contest or match specifically for a title or championship.
  • C. competedAs
    Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
  • D. hasFoughtForTitle chosen
    Indicates that an entity has participated in a contest or event specifically for a championship or title.
  • E. titleContestedIn
    Indicates that a particular title or championship is being challenged or competed for within a specific event, match, 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_69f3490819cc81909bae1f8ce99423c5 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7886be6d8819095ec62e4f2cee858 completed May 3, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69f7841440f48190b4346c08855951d2 completed May 3, 2026, 5:21 p.m.
Created at: May 1, 2026, 12:35 a.m.