Triple
T10133982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REpower 5M |
E226807
|
entity |
| Predicate | powerOutputType |
P92160
|
FINISHED |
| Object | alternating current |
—
|
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: alternating current | Statement: [REpower 5M, powerOutputType, alternating current]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerOutputType Context triple: [REpower 5M, powerOutputType, alternating current]
-
A.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
C.
powerOutputRpm
Indicates the relationship between a system’s power output and the rotational speed (in revolutions per minute) at which that power is produced.
-
D.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
E.
transmissionPowerType
Indicates the type or category of power used to transmit a signal or data between entities.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd33808048190b6023a6cd83fc179 |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:06 p.m.