Triple

T27344109
Position Surface form Disambiguated ID Type / Status
Subject ATK Sporting E684183 entity
Predicate formerParentCompanyType P192973 FINISHED
Object defense contractor 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: defense contractor | Statement: [ATK Sporting, formerParentCompanyType, defense contractor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerParentCompanyType
Context triple: [ATK Sporting, formerParentCompanyType, defense contractor]
  • A. formerParentCompany
    Indicates that one entity previously served as the parent company of another but no longer holds that status.
  • B. ultimateParentCompany
    Indicates that one company is the highest-level controlling entity in a corporate ownership structure, with no parent company above it.
  • C. laterParentCompany
    Indicates that one entity became the parent company of another entity at a later point in time, after some prior state or relationship.
  • D. hasParentCompanyType
    Indicates that an entity is associated with a parent company of a specified organizational or business type.
  • E. parentCompanyOfOrigin
    Indicates that one company is the original parent or source company from which another company was created, derived, or spun off.
  • 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_69ef1480a76481908684256ddd5bfda3 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
PDg Predicate description generation batch_69fd35d029588190a525aa8a506e7708 completed May 8, 2026, 1:01 a.m.
Created at: April 27, 2026, 11:44 a.m.