Triple
T9119581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2.5L Duratec inline-4 |
E218808
|
entity |
| Predicate | exhaustSystem |
P32744
|
FINISHED |
| Object | four-into-one exhaust manifold |
—
|
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: four-into-one exhaust manifold | Statement: [2.5L Duratec inline-4, exhaustSystem, four-into-one exhaust manifold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhaustSystem Context triple: [2.5L Duratec inline-4, exhaustSystem, four-into-one exhaust manifold]
-
A.
exhaustType
chosen
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
C.
emissionsControl
Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
-
D.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
E.
engineAspiration
Indicates whether and how an engine’s intake air is boosted or modified (e.g., naturally aspirated, turbocharged, supercharged).
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a902e08190a7eb4728f32b9e1d |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.