Triple

T11411422
Position Surface form Disambiguated ID Type / Status
Subject Air Coryell offense E270379 entity
Predicate requiresPositionType P4475 FINISHED
Object strong-armed quarterback 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: strong-armed quarterback | Statement: [Air Coryell offense, requiresPositionType, strong-armed quarterback]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresPositionType
Context triple: [Air Coryell offense, requiresPositionType, strong-armed quarterback]
  • A. supportsPosition
    Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
  • B. positionHolderMust
    Indicates that a person occupying a specific position is required or obligated to perform a certain action or fulfill a particular condition.
  • C. appliesToPosition chosen
    Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
  • D. placementType
    Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
  • E. positionRestriction
    Indicates a constraint or limitation on where an entity may be located or positioned relative to something else.
  • 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_69d6aaddeaa8819088b30ef7b50598c9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8015017d08190b4020c76545556d6 completed April 9, 2026, 7:43 p.m.
PD Predicate disambiguation batch_69d7e70ffd708190b62a78ebcbce9f78 completed April 9, 2026, 5:51 p.m.
Created at: April 8, 2026, 9:34 p.m.