Triple

T11842295
Position Surface form Disambiguated ID Type / Status
Subject World Heavyweight Champion E281681 entity
Predicate wasPreviouslyContestedOver P38352 FINISHED
Object 15 rounds 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: 15 rounds | Statement: [World Heavyweight Champion, wasPreviouslyContestedOver, 15 rounds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasPreviouslyContestedOver
Context triple: [World Heavyweight Champion, wasPreviouslyContestedOver, 15 rounds]
  • A. wasContestedIn
    Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
  • B. wasContestedBetween
    Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
  • C. laterContestedBy
    Indicates that an earlier claim, decision, or statement is subsequently challenged or disputed by another party or source.
  • D. contestedBy
    Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
  • E. firstContestedIn chosen
    Indicates the event, competition, or context in which something (such as a title, office, or position) was initially challenged or competed for.
  • 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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a65a597c8190b09f57463b279afc completed April 10, 2026, 7:27 a.m.
PD Predicate disambiguation batch_69d8a254a57481908a1e6ad97919c416 completed April 10, 2026, 7:10 a.m.
Created at: April 8, 2026, 9:43 p.m.