Triple
T31713110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-3 |
E809379
|
entity |
| Predicate | typicalCoreOutletTemperature |
P164009
|
FINISHED |
| Object | about 285–290 °C |
—
|
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 285–290 °C | Statement: [BWR-3, typicalCoreOutletTemperature, about 285–290 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCoreOutletTemperature Context triple: [BWR-3, typicalCoreOutletTemperature, about 285–290 °C]
-
A.
coolantOutletTemperature
chosen
Indicates the temperature of the coolant as it exits a system, component, or process.
-
B.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
C.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
D.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
E.
productionTemperature
Indicates the temperature at which a product, material, or substance is produced or processed.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:16 p.m.