Triple
T32959783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Gas-cooled Reactor |
E843202
|
entity |
| Predicate | coolantFlowPath |
P161859
|
FINISHED |
| Object | upward through fuel channels |
—
|
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: upward through fuel channels | Statement: [Advanced Gas-cooled Reactor, coolantFlowPath, upward through fuel channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantFlowPath Context triple: [Advanced Gas-cooled Reactor, coolantFlowPath, upward through fuel channels]
-
A.
coolantFlowConfiguration
chosen
Indicates how coolant is routed or arranged to flow through a system or component.
-
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.
coolant
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
D.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
E.
coolantBoilingLocation
Indicates the place or environment where a coolant reaches its boiling point or undergoes boiling.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d17a0d88819082ad29b5ec8b2aec |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.