Triple
T35664618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotarev D-136 |
E1030528
|
entity |
| Predicate | shaftPower |
P6069
|
FINISHED |
| Object | 8200 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: 8200 kW | Statement: [Lotarev D-136, shaftPower, 8200 kW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaftPower Context triple: [Lotarev D-136, shaftPower, 8200 kW]
-
A.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
-
B.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
horsepower
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
D.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
E.
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.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fab87b481908cd08697afe3bdd7 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.