Triple
T21003317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brookhaven Graphite Research Reactor |
E517348
|
entity |
| Predicate | maximumThermalPower |
P18504
|
FINISHED |
| Object | 24 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: 24 megawatts | Statement: [Brookhaven Graphite Research Reactor, maximumThermalPower, 24 megawatts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumThermalPower Context triple: [Brookhaven Graphite Research Reactor, maximumThermalPower, 24 megawatts]
-
A.
maximumPowerDuringOperation
chosen
Indicates the highest level of power that occurs while the system or component is operating.
-
B.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
C.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
D.
maximumEnergy
Indicates the greatest amount of energy that an entity can possess, store, or output under specified conditions.
-
E.
maxSurfaceTemperature
Indicates the highest temperature that the surface of an entity can reach or sustain under specified 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3978b0819082b63a98962a673e |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.