Triple
T35754208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extreme E |
E1033396
|
entity |
| Predicate | vehiclePowerOutput |
P43755
|
FINISHED |
| Object | 400 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: 400 kW | Statement: [Extreme E, vehiclePowerOutput, 400 kW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehiclePowerOutput Context triple: [Extreme E, vehiclePowerOutput, 400 kW]
-
A.
vehiclePower
chosen
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
B.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
vehiclePowerCollection
Indicates a relationship where a vehicle is associated with a set or collection of its power-related components, sources, or specifications.
-
D.
powertrainOutput
Indicates the relationship where a powertrain produces or delivers mechanical or electrical output (such as torque, power, or motion) to another component or system.
-
E.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a199ab248190acb81776a46011bf |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.