Triple
T17196378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic Simplified Boiling Water Reactor |
E417360
|
entity |
| Predicate | steamSupply |
P49241
|
FINISHED |
| Object | direct cycle to turbine |
—
|
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: direct cycle to turbine | Statement: [Economic Simplified Boiling Water Reactor, steamSupply, direct cycle to turbine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: steamSupply Context triple: [Economic Simplified Boiling Water Reactor, steamSupply, direct cycle to turbine]
-
A.
supplyType
chosen
Indicates the kind or category of supply associated with or provided in a given relationship or context.
-
B.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
-
C.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
D.
isReservoirOn
Indicates that a reservoir is physically located on or situated atop another specified entity or structure.
-
E.
fuelSupplier
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
- 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.