Triple
T319900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Griffon |
E7790
|
entity |
| Predicate | supercharger |
P8250
|
FINISHED |
| Object | two-stage 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: two-stage supercharger | Statement: [Rolls-Royce Griffon, supercharger, two-stage supercharger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supercharger Context triple: [Rolls-Royce Griffon, supercharger, two-stage supercharger]
-
A.
superchargerType
chosen
Indicates the specific kind or category of supercharger associated with or used by an entity.
-
B.
fastChargingCapability
Indicates that an entity has the ability to charge at a higher-than-standard power rate, significantly reducing the time needed to reach a usable or full charge.
-
C.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
D.
onboardACCharger
Indicates that an entity is equipped with an AC (alternating current) charger that is built into the system or vehicle itself.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea7edbc48190b9031bd1af48f72a |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.