Triple

T25849157
Position Surface form Disambiguated ID Type / Status
Subject Windsor Assembly Plant E651151 entity
Predicate hasCorporatePredecessor P37738 FINISHED
Object Chrysler Canada 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: Chrysler Canada | Statement: [Windsor Assembly Plant, hasCorporatePredecessor, Chrysler Canada]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCorporatePredecessor
Context triple: [Windsor Assembly Plant, hasCorporatePredecessor, Chrysler Canada]
  • A. hasCorporateSuccessor
    Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
  • B. predecessorCompany
    Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
  • C. 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.
  • D. underlyingCompanyPredecessor
    Indicates that one company served as a predecessor entity to another company in an underlying or foundational corporate relationship.
  • E. employerPredecessorName
    Indicates that the referenced name identifies a previous employer of the entity in question.
  • 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_69e7ab39035c8190be15c8aaee1bb858 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: April 22, 2026, 7:58 a.m.