Triple
T36108979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERS (MGU-K and MGU-H) |
E1044437
|
entity |
| Predicate | maximumMGU-KRecoveryPerLap |
P193803
|
FINISHED |
| Object | 2 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: 2 MJ | Statement: [ERS (MGU-K and MGU-H), maximumMGU-KRecoveryPerLap, 2 MJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumMGU-KRecoveryPerLap Context triple: [ERS (MGU-K and MGU-H), maximumMGU-KRecoveryPerLap, 2 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.
maximumSlip
Indicates the greatest allowable or observed amount of slip between two contacting or interacting elements in a system.
-
D.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- F. None of above. chosen
Provenance (4 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4:08 p.m.