Triple

T14074834
Position Surface form Disambiguated ID Type / Status
Subject Beast Quake run vs New Orleans Saints E338703 entity
Predicate ballSecurity P112723 FINISHED
Object Lynch remained on his feet without fumbling 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: Lynch remained on his feet without fumbling | Statement: [Beast Quake run vs New Orleans Saints, ballSecurity, Lynch remained on his feet without fumbling]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ballSecurity
Context triple: [Beast Quake run vs New Orleans Saints, ballSecurity, Lynch remained on his feet without fumbling]
  • A. ballSecurityError
    Indicates that an error has occurred in enforcing or maintaining security constraints related to a ball-handling or ball-access operation.
  • B. securityAccess
    Indicates that one entity has permission, authorization, or the ability to access or interact with another entity in a security-controlled context.
  • C. testSecurity
    Indicates that an entity performs actions to evaluate or verify the security properties, vulnerabilities, or protections of another entity or system.
  • D. securityAspect
    Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
  • E. securityScope
    Indicates the range or extent of protection, permissions, or access control that applies within a given security context.
  • 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5c5bc49881909012b66fa451f495 completed April 14, 2026, 3:25 p.m.
PD Predicate disambiguation batch_69de05b0e6c88190a819eeba0028981f completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de2398856c81908bed6070e4ca6ab1 completed April 14, 2026, 11:23 a.m.
Created at: April 9, 2026, 10:21 p.m.