Triple

T28556846
Position Surface form Disambiguated ID Type / Status
Subject Legion of Boom defense era E723029 entity
Predicate defensiveRanking P172122 FINISHED
Object led NFL in points allowed 2012 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: led NFL in points allowed 2012 | Statement: [Legion of Boom defense era, defensiveRanking, led NFL in points allowed 2012]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defensiveRanking
Context triple: [Legion of Boom defense era, defensiveRanking, led NFL in points allowed 2012]
  • A. defensiveRecord chosen
    Indicates a relationship where one entity documents, tracks, or summarizes the defensive performance or actions of another entity (such as a player, team, or system).
  • B. defensiveSide
    Indicates which entity is acting in a defensive role or position relative to another entity or situation.
  • C. defensiveSuccess
    Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
  • D. defensiveRole
    Indicates that an entity serves a protective or guarding function in relation to another entity or context.
  • E. defensiveSkillEmphasized
    Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
  • 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_69f01a60204481909af1bb76247b8221 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f6c1265c208190aacd2b551f8f0f82 completed May 3, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69f6bd2415fc81908c23c311aebce66f completed May 3, 2026, 3:12 a.m.
Created at: April 28, 2026, 3:46 a.m.