Triple
T36108978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERS (MGU-K and MGU-H) |
E1044437
|
entity |
| Predicate | maximumMGU-KEnergyPerLap |
P118392
|
FINISHED |
| Object | 4 MJ |
—
|
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: 4 MJ | Statement: [ERS (MGU-K and MGU-H), maximumMGU-KEnergyPerLap, 4 MJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumMGU-KEnergyPerLap Context triple: [ERS (MGU-K and MGU-H), maximumMGU-KEnergyPerLap, 4 MJ]
-
A.
maximumMGU-KPowerOutput
Indicates the highest electrical power output capacity that an MGU-K (motor generator unit – kinetic) is allowed or able to deliver.
-
B.
MGU-HFunction
Indicates a functional or operational relationship defined within the MGU system, where one element acts as a function that determines or transforms the state or value of another.
-
C.
usesKERS
Indicates that one entity employs or relies on a Kinetic Energy Recovery System (KERS) as part of its operation or functionality.
-
D.
maximumTurboPower
Indicates the highest level of turbo power that can be achieved or utilized in the given context.
-
E.
maximumEnergy
chosen
Indicates the greatest amount of energy that an entity can possess, store, or output 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:08 p.m.