Triple

T136104
Position Surface form Disambiguated ID Type / Status
Subject Saturn E2749 entity
Predicate attemptedSaleOutcome P4339 FINISHED
Object sale to Penske Automotive Group failed in 2009 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: sale to Penske Automotive Group failed in 2009 | Statement: [Saturn, attemptedSaleOutcome, sale to Penske Automotive Group failed in 2009]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: attemptedSaleOutcome
Context triple: [Saturn, attemptedSaleOutcome, sale to Penske Automotive Group failed in 2009]
  • A. declinedDuring
    Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
  • B. soldCompanyTo
    Indicates that one entity transferred ownership of a company to another entity through a sale transaction.
  • C. finalDisposition chosen
    Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
  • D. concludedAt
    Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
  • E. rejectedOrModifiedBy
    Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
  • 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.