Triple
T9543935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vestas V80 |
E230232
|
entity |
| Predicate | powerConversion |
P37195
|
FINISHED |
| Object | mechanical-to-electrical |
—
|
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: mechanical-to-electrical | Statement: [Vestas V80, powerConversion, mechanical-to-electrical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerConversion Context triple: [Vestas V80, powerConversion, mechanical-to-electrical]
-
A.
powerConversionMethod
chosen
Indicates the method or process by which one form of power or energy is converted into another.
-
B.
relationToWatt
Indicates a relationship that specifies how something is connected or related to Watt, such as by association, reference, or contextual linkage.
-
C.
usesEnergyConversion
Indicates that an entity performs or involves a process where one form of energy is transformed into another to achieve a function or outcome.
-
D.
transferredPowerTo
Indicates that one entity has passed control, authority, or energy to another entity.
-
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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98ebd4148190b71b134d7545fe35 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.