Triple

T38620033
Position Surface form Disambiguated ID Type / Status
Subject 2023 Call of Duty League season E936841 entity
Predicate MVPRealName P9233 FINISHED
Object Paco Rusiewiez 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: Paco Rusiewiez | Statement: [2023 Call of Duty League season, MVPRealName, Paco Rusiewiez]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: MVPRealName
Context triple: [2023 Call of Duty League season, MVPRealName, Paco Rusiewiez]
  • A. MVPInGameName
    Indicates that a particular in-game name belongs to or is used by the player who was awarded MVP (Most Valuable Player) in a specific game or match.
  • B. MVPtrophyName
    Indicates the name or title assigned to a specific MVP (Most Valuable Player) trophy.
  • C. realName chosen
    Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
  • D. MVPType
    Indicates the specific category or role of a person or entity designated as the “Most Valuable Player” (MVP) within a given context or system.
  • E. MVP
    Indicates that an entity has been selected or recognized as the “Most Valuable Player,” i.e., the most outstanding or impactful participant within a specific game, season, event, 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_69f76ed403208190b862dc795171353f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdb0de8c08190928cd1323f80ab5c completed May 7, 2026, 6:33 p.m.
PD Predicate disambiguation batch_69fcd9017dd88190b32a73fe78909740 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:32 p.m.