Triple
T28016148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-320 |
E707548
|
entity |
| Predicate | coolantCirculation |
P161859
|
FINISHED |
| Object | forced circulation with main coolant pumps |
—
|
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: forced circulation with main coolant pumps | Statement: [V-320, coolantCirculation, forced circulation with main coolant pumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolantCirculation Context triple: [V-320, coolantCirculation, forced circulation with main coolant pumps]
-
A.
coolant
Indicates that one entity functions as a coolant for another, serving to absorb and remove heat from it.
-
B.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
C.
coolantFlowConfiguration
chosen
Indicates how coolant is routed or arranged to flow through a system or component.
-
D.
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.
-
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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:07 p.m.