Triple

T35905697
Position Surface form Disambiguated ID Type / Status
Subject UFC Welterweight Championship E1038465 entity
Predicate isMainEventWhenDefended P184225 FINISHED
Object usually 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: usually | Statement: [UFC Welterweight Championship, isMainEventWhenDefended, usually]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMainEventWhenDefended
Context triple: [UFC Welterweight Championship, isMainEventWhenDefended, usually]
  • A. defendedAtEvent
    Indicates that an entity (typically a work, thesis, or position) was formally defended or argued for during a specific event.
  • B. isDefendedOn
    Indicates that one entity provides protection, justification, or support for another entity in a specific context or situation.
  • C. isDefendedAt
    Indicates that a particular entity is protected or justified at a specific time, place, or context.
  • D. mainEventStipulation
    Indicates that a specified condition, requirement, or rule must be satisfied for the main event or primary occurrence in a given context.
  • E. canBeDefendedIn
    Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
  • 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_69f76e2259608190bf6788a132e0d139 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7acaec1508190a38f2ac9cc5383e7 completed May 3, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69f7ab734d848190a84f9b8c3a952b75 completed May 3, 2026, 8:09 p.m.
PDg Predicate description generation batch_69f7ac2210e481909279dade5328825c completed May 3, 2026, 8:12 p.m.
Created at: May 3, 2026, 4:07 p.m.