Triple
T9410195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens SWT-3.6-107 |
E226684
|
entity |
| Predicate | ratedPower |
P10373
|
FINISHED |
| Object | 3.6 MW |
—
|
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: 3.6 MW | Statement: [Siemens SWT-3.6-107, ratedPower, 3.6 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratedPower Context triple: [Siemens SWT-3.6-107, ratedPower, 3.6 MW]
-
A.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
maximumPowerDuringOperation
Indicates the highest level of power that occurs while the system or component is operating.
-
C.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
D.
designPowerOutput
chosen
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
E.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5255e4fc81908bf2f69c9a12ef83 |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.