Triple
T36108976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERS (MGU-K and MGU-H) |
E1044437
|
entity |
| Predicate | maximumMGU-KPowerOutput |
P193686
|
FINISHED |
| Object | 120 kW |
—
|
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: 120 kW | Statement: [ERS (MGU-K and MGU-H), maximumMGU-KPowerOutput, 120 kW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumMGU-KPowerOutput Context triple: [ERS (MGU-K and MGU-H), maximumMGU-KPowerOutput, 120 kW]
-
A.
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.
-
B.
maximumTurboPower
Indicates the highest level of turbo power that can be achieved or utilized in the given context.
-
C.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
-
D.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
E.
maximumContinuousPowerRPM
Indicates the engine speed, in revolutions per minute, at which the system can continuously deliver its maximum allowable power without exceeding operational limits.
- 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_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 3, 2026, 4:08 p.m.