Triple
T17804256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancia Delta |
E444512
|
entity |
| Predicate | thirdGenerationEndOfProduction |
P25156
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Lancia Delta, thirdGenerationEndOfProduction, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdGenerationEndOfProduction Context triple: [Lancia Delta, thirdGenerationEndOfProduction, 2014]
-
A.
thirdGenerationEnd
chosen
Indicates that a third generation in a sequence, lineage, or process has reached its endpoint or conclusion.
-
B.
thirdGenerationProduction
Indicates that the subject is involved in producing or manufacturing items belonging to the third generation of a product, technology, or design series.
-
C.
thirdGeneration
Indicates that one entity is the grandchild (third generation) relative to another entity in a lineage or succession.
-
D.
thirdGenerationMarketedAs
Indicates that something is promoted or labeled as being in its third generation within a series or product line.
-
E.
thirdGenerationReleaseDate
Indicates the date on which the third generation of an item, product, or entity was officially released.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48802bcfc8190a138164d11081ab8 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.