Triple
T37155469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dounreay |
E920484
|
entity |
| Predicate | coolantUsed |
P10369
|
FINISHED |
| Object | liquid sodium |
—
|
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: liquid sodium | Statement: [Dounreay, coolantUsed, liquid sodium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantUsed Context triple: [Dounreay, coolantUsed, liquid sodium]
-
A.
coolant
chosen
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
B.
coolantLossOccurred
Indicates that a loss of coolant has taken place in the system or component in question.
-
C.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
D.
coolingSystemFeatures
Indicates that one entity specifies or provides particular characteristics, components, or capabilities of a cooling system associated with another entity.
-
E.
coolantFlowConfiguration
Indicates how coolant is routed or arranged to flow through a system or component.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.