Triple
T34505781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voodoo |
E885880
|
entity |
| Predicate | exhaustManifoldDesign |
P32744
|
FINISHED |
| Object | tuned long-tube style headers |
—
|
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: tuned long-tube style headers | Statement: [Voodoo, exhaustManifoldDesign, tuned long-tube style headers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhaustManifoldDesign Context triple: [Voodoo, exhaustManifoldDesign, tuned long-tube style headers]
-
A.
exhaustType
chosen
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
combustionChamberDesign
Indicates the specific configuration and structural characteristics of a combustion chamber that determine how fuel and oxidizer mix, ignite, and burn within an engine or reactor.
-
C.
exhaustMaterial
Indicates that one entity uses up or depletes the material resources or substance of another entity through some process or action.
-
D.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
E.
exhaustDirection
Indicates the direction in which exhaust gases or emissions are released or discharged from a source.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.