Triple
T2614764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldsmobile Toronado |
E58860
|
entity |
| Predicate | thirdGenerationYears |
P25155
|
FINISHED |
| Object | 1979–1992 |
—
|
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: 1979–1992 | Statement: [Oldsmobile Toronado, thirdGenerationYears, 1979–1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdGenerationYears Context triple: [Oldsmobile Toronado, thirdGenerationYears, 1979–1992]
-
A.
thirdGenerationReleaseDate
Indicates the date on which the third generation of an item, product, or entity was officially released.
-
B.
thirdGenerationStart
chosen
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
C.
secondGenerationStartYear
Indicates the calendar year in which the second generation of something (e.g., a product, model, or series) begins.
-
D.
thirdGenerationPlatform
Indicates that the subject is a third-generation instance or version within a sequence of related platforms.
-
E.
thirdGenerationName
Indicates that the object is the name or designation assigned to the third generation in a lineage or sequence associated with the subject.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.