Triple
T29865367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens SWT-2.3-93 |
E758440
|
entity |
| Predicate | rotorDiameterClass |
P22940
|
FINISHED |
| Object | 90–100 m 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: 90–100 m class | Statement: [Siemens SWT-2.3-93, rotorDiameterClass, 90–100 m class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorDiameterClass Context triple: [Siemens SWT-2.3-93, rotorDiameterClass, 90–100 m class]
-
A.
rotorDiameter
chosen
Indicates the relationship where a rotor is associated with a specific measurement representing the diameter of its circular span.
-
B.
propellerDiameter_m
Indicates the diameter measurement of a propeller, expressed in meters.
-
C.
rotorType
Indicates the specific kind or category of rotor associated with an entity.
-
D.
fairingDiameterClass
Indicates the classification of an object based on the size range of its fairing diameter.
-
E.
rotorSpeedTypical
Indicates the usual or characteristic rotational speed associated with a rotor under normal or standard operating conditions.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67688760481908e28d887d583e8c4 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:51 p.m.