Triple
T16384975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-4 |
E397896
|
entity |
| Predicate | coolantBoilingLocation |
P123189
|
FINISHED |
| Object | inside reactor core |
—
|
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: inside reactor core | Statement: [BWR-4, coolantBoilingLocation, inside reactor core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantBoilingLocation Context triple: [BWR-4, coolantBoilingLocation, inside reactor core]
-
A.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
B.
coolant
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
C.
hasBoilerPosition
Indicates the spatial placement or designated location of a boiler relative to another object or within a given environment.
-
D.
coolantLossOccurred
Indicates that a loss of coolant has taken place in the system or component in question.
-
E.
airIntakeLocation
Indicates the physical position or area where air is drawn into a system, device, or structure.
- F. None of above. chosen
Provenance (4 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263c60088190b85a8c02bc3ef315 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.