Triple
T17196358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic Simplified Boiling Water Reactor |
E417360
|
entity |
| Predicate | usesNaturalCirculation |
P11564
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Economic Simplified Boiling Water Reactor, usesNaturalCirculation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNaturalCirculation Context triple: [Economic Simplified Boiling Water Reactor, usesNaturalCirculation, true]
-
A.
usesWorkingFluid
Indicates that one entity operates or functions by employing another entity as its working fluid.
-
B.
hasCoolingFlow
Indicates that an entity is equipped with or utilizes a system or mechanism to remove heat or maintain a lower temperature through the flow of a cooling medium.
-
C.
isNaturalIn
Indicates that something occurs, exists, or develops in a place or context as a native or inherent part of it, without artificial introduction.
-
D.
circulatesIn
Indicates that something moves or flows repeatedly within a particular space, system, or medium.
-
E.
coolingMethod
chosen
Indicates the technique or process used to remove heat from something or keep it at a lower temperature.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daab57c819093496cbdc7890f34 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.