Triple

T13626674
Position Surface form Disambiguated ID Type / Status
Subject Baltimore Colts offense E325599 entity
Predicate secondaryStrength P111359 FINISHED
Object play-action passing 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: play-action passing | Statement: [Baltimore Colts offense, secondaryStrength, play-action passing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryStrength
Context triple: [Baltimore Colts offense, secondaryStrength, play-action passing]
  • A. side2Strength
    Indicates the magnitude or level of strength associated with the second side in a relationship, comparison, or interaction.
  • B. secondaryTo
    Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
  • C. secondarySee
    Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
  • D. secondaryTone
    Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
  • E. secondaryState
    Indicates that an entity is in a subordinate or less primary condition, status, or mode relative to its main or primary state.
  • 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc60635d08190899806fe8936f02a completed April 12, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69dbbe85e1c4819095194f4b7f9f6118 completed April 12, 2026, 3:47 p.m.
PDg Predicate description generation batch_69dbc6043e148190a2a25f929cfa35e5 completed April 12, 2026, 4:19 p.m.
Created at: April 9, 2026, 9:51 p.m.