Triple

T5266967
Position Surface form Disambiguated ID Type / Status
Subject NFL Defensive Rookie of the Year E118959 entity
Predicate typicalPositionGroups P29748 FINISHED
Object linebacker 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: linebacker | Statement: [NFL Defensive Rookie of the Year, typicalPositionGroups, linebacker]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalPositionGroups
Context triple: [NFL Defensive Rookie of the Year, typicalPositionGroups, linebacker]
  • A. positionGroup chosen
    Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
  • B. traditionalPositions
    Indicates that one entity holds or is associated with customary or historically established roles, stances, or arrangements in relation to another entity.
  • C. typicalPositionBias
    Indicates a systematic tendency for something to be placed, chosen, or interpreted in a commonly favored or default position relative to other options.
  • D. typicalCalendarPosition
    Indicates the usual or standard placement of something within a calendar sequence, such as its customary date, time, or ordering.
  • E. typicalRecipientPosition
    Indicates the usual or expected spatial or organizational position where a recipient is located relative to the action or source.
  • 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_69bd446a42c88190b7ecbef006561d55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7d5a23908190a24e79d1b29d6fcf completed March 20, 2026, 5:01 p.m.
PD Predicate disambiguation batch_69bd77c71268819094f9f5203eed392d completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:51 p.m.