Triple
T16181756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Focus |
E392697
|
entity |
| Predicate | discontinuationYearInUnitedStates |
P1466
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Ford Focus, discontinuationYearInUnitedStates, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discontinuationYearInUnitedStates Context triple: [Ford Focus, discontinuationYearInUnitedStates, 2018]
-
A.
discontinuationAnnouncementYear
Indicates the year in which the discontinuation of something (such as a product, service, or program) was officially announced.
-
B.
hasDiscontinuationApproxYear
Indicates that an entity ceased to exist, operate, or be available around a specified (approximate) calendar year.
-
C.
discontinuationDateNorthAmerica
Indicates the date on which something stops being available or in use specifically within North America.
-
D.
brandDiscontinuationYear
Indicates the year in which a brand ceased operations or was officially discontinued.
-
E.
discontinuedIn
chosen
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205d858c8190802d44e08e3cdcd6 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.