Triple
T33406210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai E-GMP |
E855443
|
entity |
| Predicate | maxTorqueOutput |
P94481
|
FINISHED |
| Object | over 700 Nm depending on configuration |
—
|
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: over 700 Nm depending on configuration | Statement: [Hyundai E-GMP, maxTorqueOutput, over 700 Nm depending on configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxTorqueOutput Context triple: [Hyundai E-GMP, maxTorqueOutput, over 700 Nm depending on configuration]
-
A.
maximumTorque
chosen
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
-
B.
maximumTorqueRpm
Indicates the engine speed, in revolutions per minute, at which the maximum torque is produced.
-
C.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
D.
maximumContinuousPowerRPM
Indicates the engine speed, in revolutions per minute, at which the system can continuously deliver its maximum allowable power without exceeding operational limits.
-
E.
torque
Indicates a rotational force applied by one entity on another around a pivot or axis.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.