Triple

T725399
Position Surface form Disambiguated ID Type / Status
Subject Ed Hochuli E14713 entity
Predicate hasNotableIncident P18677 FINISHED
Object 2008 Chargers–Broncos blown fumble call 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: 2008 Chargers–Broncos blown fumble call | Statement: [Ed Hochuli, hasNotableIncident, 2008 Chargers–Broncos blown fumble call]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableIncident
Context triple: [Ed Hochuli, hasNotableIncident, 2008 Chargers–Broncos blown fumble call]
  • A. notableProtectiveIncident
    Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
  • B. hasNotableIssue
    Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
  • C. hasNotableImpact
    Indicates that one entity exerts a significant or noteworthy influence or effect on another entity or context.
  • D. hasNotableHazard
    Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
  • E. hasNotableFeature
    Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
  • 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_69a4934c753c81909b309027e48b9b3a completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a5a7fb7c819096db848fe2ba246a completed March 1, 2026, 8:46 p.m.
PD Predicate disambiguation batch_69a4a4f700cc81908c6de3eedf68433c completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a55a26e081908134ee93faaf7c40 completed March 1, 2026, 8:45 p.m.
Created at: March 1, 2026, 7:37 p.m.