Triple
T10498489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SACM V8X-1500 Hyperbar diesel engine |
E247604
|
entity |
| Predicate | powerDensity |
P94484
|
FINISHED |
| Object | high for its class |
—
|
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: high for its class | Statement: [SACM V8X-1500 Hyperbar diesel engine, powerDensity, high for its class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDensity Context triple: [SACM V8X-1500 Hyperbar diesel engine, powerDensity, high for its class]
-
A.
powerConcentration
Indicates the degree to which authority or control is centralized in a single entity or small group rather than being widely distributed.
-
B.
energyConcentration
Indicates a relationship where energy is gathered, focused, or accumulated within a specific region, object, or system.
-
C.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
D.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
E.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098e45ec8190a02b981a06786909 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:25 p.m.