Triple
T34194507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth GTX |
E877200
|
entity |
| Predicate | highPerformanceOption |
P12592
|
FINISHED |
| Object | 426 cu in Hemi V8 |
—
|
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: 426 cu in Hemi V8 | Statement: [Plymouth GTX, highPerformanceOption, 426 cu in Hemi V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highPerformanceOption Context triple: [Plymouth GTX, highPerformanceOption, 426 cu in Hemi V8]
-
A.
isHighPerformance
Indicates that an entity operates at a superior or above-standard level of efficiency, speed, or capability compared to typical expectations or benchmarks.
-
B.
notableHighPerformanceVariant
chosen
Indicates that an entity is recognized as a particularly high-performance version or variant of another entity.
-
C.
hasAfterburnerOption
Indicates that an entity offers or is equipped with an optional afterburner capability.
-
D.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
E.
supportsTurboBoost
Indicates that one entity provides or is compatible with Turbo Boost functionality for another entity or process.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710276a7c81909d292c0e73b48533 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.