Triple
T34194328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge Magnum (2005–2008) |
E877196
|
entity |
| Predicate | SRT8Engine |
P56323
|
FINISHED |
| Object | 6.1 L HEMI V8 engine |
—
|
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: 6.1 L HEMI V8 engine | Statement: [Dodge Magnum (2005–2008), SRT8Engine, 6.1 L HEMI V8 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SRT8Engine Context triple: [Dodge Magnum (2005–2008), SRT8Engine, 6.1 L HEMI V8 engine]
-
A.
engineTypeUsed
chosen
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
B.
fourthGenerationPowertrain
Indicates that the subject uses or is equipped with a fourth-generation version of a powertrain system.
-
C.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
D.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
E.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
- 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.