Triple
T2292858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth Barracuda |
E51543
|
entity |
| Predicate | secondGenerationPlatform |
P39013
|
FINISHED |
| Object | A-body |
—
|
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: A-body | Statement: [Plymouth Barracuda, secondGenerationPlatform, A-body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondGenerationPlatform Context triple: [Plymouth Barracuda, secondGenerationPlatform, A-body]
-
A.
thirdGenerationPlatform
Indicates that the subject is a third-generation instance or version within a sequence of related platforms.
-
B.
secondGenerationReleaseDate
Indicates the date on which the second generation or version of an item was officially released.
-
C.
secondGenerationEnd
Indicates the point in time or event at which the second generation of a lineage, process, or system concludes.
-
D.
secondGenerationProduction
Indicates that the production activity involves a second generation of products, technologies, or processes derived from an earlier initial generation.
-
E.
secondGenerationName
Indicates that the object is the name given to the second generation derived from the subject.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcd0d01ac8190935fe904905cb233 |
completed | March 7, 2026, 7 a.m. |
Created at: March 4, 2026, 7:48 p.m.