Triple

T36153208
Position Surface form Disambiguated ID Type / Status
Subject Interim UFC Featherweight Champion E1045648 entity
Predicate requiresWeightCut P201188 FINISHED
Object true 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: true | Statement: [Interim UFC Featherweight Champion, requiresWeightCut, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresWeightCut
Context triple: [Interim UFC Featherweight Champion, requiresWeightCut, true]
  • A. weightAfterRecut
    Indicates the resulting weight of an item or material after it has been cut, trimmed, or recut from its original form.
  • B. requiresWeighIn
    Indicates that one entity must provide an opinion, decision, or input before another entity’s action or process can proceed.
  • C. weightReductionComparedTo
    Indicates a comparison showing how much less weight one entity has relative to another.
  • D. intendedWeight
    Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
  • E. requiresOfficialWeighIn
    Indicates that an action, event, or process cannot proceed or be validated unless it is accompanied by an authorized, formally recorded measurement of weight.
  • 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_69f76e38903c8190a52887620f90aabe completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffdd05d1908190957deb11392f4595 completed May 10, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69ffdc0d33c881908b3483bee8a96540 completed May 10, 2026, 1:14 a.m.
PDg Predicate description generation batch_69ffdd0486e08190a0f2ff4ce0aee13b completed May 10, 2026, 1:19 a.m.
Created at: May 3, 2026, 4:08 p.m.