Triple
T32307834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBR-2 reactor |
E825414
|
entity |
| Predicate | peakPower |
P166971
|
FINISHED |
| Object | ~1500 MW thermal (pulse peak, order of magnitude) |
—
|
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: ~1500 MW thermal (pulse peak, order of magnitude) | Statement: [IBR-2 reactor, peakPower, ~1500 MW thermal (pulse peak, order of magnitude)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPower Context triple: [IBR-2 reactor, peakPower, ~1500 MW thermal (pulse peak, order of magnitude)]
-
A.
peakPowerCentury
Indicates that an entity achieved its highest level of power or influence during a specified century.
-
B.
peakPowerApproximateDate
Indicates the approximate date or time period when the peak power level is reached or expected to occur.
-
C.
peak
chosen
Indicates that an entity reaches its highest or maximum level, value, or intensity within a given context or period.
-
D.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
E.
keyPower
Indicates that an entity possesses a primary or controlling power, authority, or influence over another entity or process.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd8835588190b562ff2832f98acf |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.