Triple
T10324840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Galaxie designs |
E242735
|
entity |
| Predicate | notableDesignPeriodEnd |
P14397
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Ford Galaxie designs, notableDesignPeriodEnd, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDesignPeriodEnd Context triple: [Ford Galaxie designs, notableDesignPeriodEnd, 1974]
-
A.
yearOfCreationEnd
Indicates the year in which the creation or production of something was completed or came to an end.
-
B.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
C.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
D.
designPeriod
chosen
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
E.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.