Triple

T136016
Position Surface form Disambiguated ID Type / Status
Subject Holden E2747 entity
Predicate corporateForm P64 FINISHED
Object subsidiary 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: subsidiary | Statement: [Holden, corporateForm, subsidiary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: corporateForm
Context triple: [Holden, corporateForm, subsidiary]
  • A. company
    Indicates that an entity is a business organization engaged in commercial, industrial, or professional activities.
  • B. legalPersonality
    Indicates that an entity possesses recognized legal status, enabling it to hold rights, bear obligations, and act as a subject under the law.
  • C. organizationType
    Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
  • D. legalForm chosen
    Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
  • E. employerType
    Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
  • 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_69a2520c0f3481908b0ed054a2fca8d0 completed Feb. 28, 2026, 2:25 a.m.
NER Named-entity recognition batch_69a257a4edf081908c494c8370c76b9a completed Feb. 28, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69a25651b9048190a6277b7fec98c1ea completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:30 a.m.