Triple
T34194506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth GTX |
E877200
|
entity |
| Predicate | standardEngine |
P2092
|
FINISHED |
| Object | 440 cu in 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: 440 cu in V8 | Statement: [Plymouth GTX, standardEngine, 440 cu in V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardEngine Context triple: [Plymouth GTX, standardEngine, 440 cu in V8]
-
A.
typicalEngine
chosen
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
B.
standardEditionVolume
Indicates that one entity is a volume that forms part of a standard edition of another entity (such as a work or collection).
-
C.
standardExample
Indicates that something is a typical or canonical instance used to illustrate a general case or concept.
-
D.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
E.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
- 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_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:55 a.m.