Triple

T1211379
Position Surface form Disambiguated ID Type / Status
Subject Ford Model N E26006 entity
Predicate roleInCompanyHistory P25024 FINISHED
Object direct predecessor line to the Ford Model T 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: direct predecessor line to the Ford Model T | Statement: [Ford Model N, roleInCompanyHistory, direct predecessor line to the Ford Model T]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInCompanyHistory
Context triple: [Ford Model N, roleInCompanyHistory, direct predecessor line to the Ford Model T]
  • A. workedAs
    Indicates that an entity held a particular job, role, or position, performing work in that capacity.
  • B. roleInIndustry
    Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
  • C. hasOrganizationalRole
    Indicates that an entity holds a specific role, position, or function within an organization.
  • D. hasHistoricIndustry
    Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
  • E. roleInLeagueHistory
    Indicates the specific function, contribution, or significance an entity has had within the historical development or narrative of a league.
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bde581308190bbe30683bf6c48c3 completed March 1, 2026, 10:29 p.m.
PD Predicate disambiguation batch_69a4bb62a7c08190a79dcb6ff72ac99b completed March 1, 2026, 10:19 p.m.
PDg Predicate description generation batch_69a4bc6d5b7881908091e40c8695ef53 completed March 1, 2026, 10:23 p.m.
Created at: March 1, 2026, 7:46 p.m.