Triple
T4703966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L Reactor |
E104343
|
entity |
| Predicate | designedThermalPower |
P10373
|
FINISHED |
| Object | approximately 2,800 MWth |
—
|
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: approximately 2,800 MWth | Statement: [L Reactor, designedThermalPower, approximately 2,800 MWth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedThermalPower Context triple: [L Reactor, designedThermalPower, approximately 2,800 MWth]
-
A.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
B.
designPowerOutput
chosen
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
D.
netElectricalCapacity_MWe
Indicates the relationship specifying an entity’s net electrical power generation capacity, measured in megawatts electric (MWe), after accounting for internal power consumption.
-
E.
designEnergy
Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.