Triple
T1926600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM EcoTec3 V8 |
E40845
|
entity |
| Predicate | displacementVariant |
P33537
|
FINISHED |
| Object | 5.3L |
—
|
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: 5.3L | Statement: [GM EcoTec3 V8, displacementVariant, 5.3L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementVariant Context triple: [GM EcoTec3 V8, displacementVariant, 5.3L]
-
A.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
B.
displacementClass
Indicates the category or type of physical displacement associated with an entity or event, typically grouping similar kinds or magnitudes of movement into a common class.
-
C.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
D.
plannedDisplacement
Indicates a deliberate, pre-arranged movement or relocation of an entity from one place or state to another.
-
E.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb261ef8481909be2390ac5a02622 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb20c4970819086e66a5435744297 |
completed | March 7, 2026, 5:05 a.m. |
Created at: March 4, 2026, 7:35 p.m.