Triple

T3527648
Position Surface form Disambiguated ID Type / Status
Subject Super Bowl XII E74578 entity
Predicate sacksByCowboysDefense P49279 FINISHED
Object 4 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: 4 | Statement: [Super Bowl XII, sacksByCowboysDefense, 4]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sacksByCowboysDefense
Context triple: [Super Bowl XII, sacksByCowboysDefense, 4]
  • A. sackTotalNFL
    Indicates the total number of quarterback sacks recorded in NFL play for the given entity.
  • B. sacks
    Indicates that one entity tackles and brings another entity to the ground, typically behind a line of scrimmage or in a way that stops their progress.
  • C. RavensDefensiveTouchdowns
    Indicates the number of touchdowns scored by the Ravens’ defense, typically by returning interceptions, fumbles, or blocked kicks for a score.
  • D. cowboysTurnovers
    Indicates the number of times the Cowboys lose possession of the ball to the opposing team through fumbles or interceptions.
  • E. defensiveTackle
    Indicates that an entity plays the defensive tackle position, typically lining up on the interior of the defensive line to disrupt offensive plays.
  • 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_69ad85d0c5488190a3d8e02ebd01a1aa completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc6d099c8190b2b1e65a56e52089 completed March 8, 2026, 6:14 p.m.
PD Predicate disambiguation batch_69adae121a048190b03825a001d21f49 completed March 8, 2026, 5:12 p.m.
PDg Predicate description generation batch_69adb21a437c81908bca88d5e123d744 completed March 8, 2026, 5:30 p.m.
Created at: March 8, 2026, 3:19 p.m.