Triple

T1452842
Position Surface form Disambiguated ID Type / Status
Subject World Welterweight Title E31331 entity
Predicate requiresWeighInLimit P26160 FINISHED
Object 147 pounds at official weigh-in 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: 147 pounds at official weigh-in | Statement: [World Welterweight Title, requiresWeighInLimit, 147 pounds at official weigh-in]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresWeighInLimit
Context triple: [World Welterweight Title, requiresWeighInLimit, 147 pounds at official weigh-in]
  • A. weightLimitInPounds chosen
    Indicates the maximum allowable weight for something, expressed in pounds.
  • B. weightLimitInKilograms
    Indicates the maximum allowable weight for something, expressed in kilograms.
  • C. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • D. requiresCheckIn
    Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
  • E. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69a499171a28819085b993a3ac78e363 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c57d34cc8190801b769d9d9b2e2e completed March 1, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69a4c47cdbd0819092022344a2f4ad7b completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8 p.m.