Triple
T9009581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentley Speed Six |
E215432
|
entity |
| Predicate | carburetion |
P8247
|
FINISHED |
| Object | twin SU carburettors |
—
|
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: twin SU carburettors | Statement: [Bentley Speed Six, carburetion, twin SU carburettors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carburetion Context triple: [Bentley Speed Six, carburetion, twin SU carburettors]
-
A.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
B.
engineAspiration
Indicates whether and how an engine’s intake air is boosted or modified (e.g., naturally aspirated, turbocharged, supercharged).
-
C.
fuelSystem
chosen
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
D.
carbonation
Indicates that a substance, typically a beverage, has been infused with carbon dioxide gas, resulting in bubbles or fizziness.
-
E.
combustionType
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
- 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69c00ae8819090786385a72e8baf |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:06 p.m.