Triple
T17196359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic Simplified Boiling Water Reactor |
E417360
|
entity |
| Predicate | primaryCirculationPumps |
P5505
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Economic Simplified Boiling Water Reactor, primaryCirculationPumps, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCirculationPumps Context triple: [Economic Simplified Boiling Water Reactor, primaryCirculationPumps, none]
-
A.
primaryCircuits
Indicates that one entity functions as a main or principal circuit in relation to another entity.
-
B.
primaryRegionOfCirculation
Indicates the main geographic or political region in which something (such as a currency, publication, or product) is predominantly circulated or used.
-
C.
primaryCircuit
Indicates that one entity functions as the main or first-stage electrical path or loop in relation to another system or circuit.
-
D.
primaryVessels
Indicates that the related vessels are the main or principal ones within a given system, structure, or context.
-
E.
numberOfPumps
chosen
Indicates the quantity of pumps associated with or required by an entity or system.
- 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.