Triple
T28858256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birkin Blower |
E728794
|
entity |
| Predicate | forcedInduction |
P84513
|
FINISHED |
| Object | Roots-type supercharger |
—
|
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: Roots-type supercharger | Statement: [Birkin Blower, forcedInduction, Roots-type supercharger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedInduction Context triple: [Birkin Blower, forcedInduction, Roots-type supercharger]
-
A.
compressionIgnition
Indicates that an engine or combustion process is initiated by compressing the fuel–air mixture until it self-ignites, rather than by an external spark.
-
B.
engineAspiration
chosen
Indicates whether and how an engine’s intake air is boosted or modified (e.g., naturally aspirated, turbocharged, supercharged).
-
C.
hasTurbocharger
Indicates that an engine or vehicle is equipped with a turbocharger that boosts its air intake and performance.
-
D.
turbochargerType
Indicates the specific kind or classification of turbocharger associated with an engine or system.
-
E.
gForce
Indicates the gravitational or inertial acceleration experienced by an object, typically expressed as a multiple of standard gravity.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a14eaa081908113d246dbaf86dd |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:46 a.m.