Triple
T22756583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peugeot 9X8 |
E562858
|
entity |
| Predicate | frontMotorPowerOutput |
P149615
|
FINISHED |
| Object | 200 kW (approximate, subject to BoP) |
—
|
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: 200 kW (approximate, subject to BoP) | Statement: [Peugeot 9X8, frontMotorPowerOutput, 200 kW (approximate, subject to BoP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontMotorPowerOutput Context triple: [Peugeot 9X8, frontMotorPowerOutput, 200 kW (approximate, subject to BoP)]
-
A.
electricMotorPosition
Indicates the rotational position or angle of an electric motor at a given moment.
-
B.
frontEnginePosition
Indicates that the engine of a vehicle is located at the front portion of the vehicle.
-
C.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
-
D.
motorPosition
Indicates the specific location or angle at which a motor’s moving component is currently set.
-
E.
powerOutputRpm
Indicates the relationship between a system’s power output and the rotational speed (in revolutions per minute) at which that power is produced.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bd22588190ac724a656194f5b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:25 p.m.