Triple

T26425365
Position Surface form Disambiguated ID Type / Status
Subject Dayton Company E664356 entity
Predicate hasCorporateDescendant P37738 FINISHED
Object Target Corporation NE NERFINISHED

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: Target Corporation | Statement: [Dayton Company, hasCorporateDescendant, Target Corporation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCorporateDescendant
Context triple: [Dayton Company, hasCorporateDescendant, Target Corporation]
  • A. isCorporatePrecursorOf chosen
    Indicates that one corporate entity is a predecessor in the organizational or legal lineage of another corporate entity, such as through merger, acquisition, or reorganization.
  • B. hasParentCompany
    Indicates that one company is owned or controlled by another company that serves as its parent organization.
  • C. hasParentCompanyRole
    Indicates that an entity holds a specific role or function within its parent company in a corporate hierarchy.
  • D. hasParentCompanyType
    Indicates that an entity is associated with a parent company of a specified organizational or business type.
  • E. hasParentCompanyBusiness
    Indicates that one company operates as a business owned or controlled by another company that serves as its parent company.
  • 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_69ee883ad6a4819088f918e76122d690 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69fd9ff026a48190bfec33deeb3b2c43 completed May 8, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69fd97d805bc8190ba12f429d3ad04c7 completed May 8, 2026, 7:59 a.m.
Created at: April 26, 2026, 11:45 p.m.