Triple
T18127284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITER |
E433908
|
entity |
| Predicate | designedInputHeatingPower |
P10373
|
FINISHED |
| Object | about 50 megawatts |
—
|
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: about 50 megawatts | Statement: [ITER, designedInputHeatingPower, about 50 megawatts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedInputHeatingPower Context triple: [ITER, designedInputHeatingPower, about 50 megawatts]
-
A.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
B.
designPowerOutput
chosen
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
hasHeating
Indicates that an entity is equipped with or provides a heating system or heating capability.
-
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.
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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddef4cd88190b16ef0d6ed3968c6 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.