Triple
T27248212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matimba Power Station |
E687408
|
entity |
| Predicate | usesCooling |
P11564
|
FINISHED |
| Object | air-cooled condenser |
—
|
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: air-cooled condenser | Statement: [Matimba Power Station, usesCooling, air-cooled condenser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCooling Context triple: [Matimba Power Station, usesCooling, air-cooled condenser]
-
A.
coolingRequirement
Indicates that an entity requires or is subject to a specific amount or type of cooling to operate within acceptable conditions.
-
B.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
-
C.
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.
-
D.
coolingMethod
chosen
Indicates the technique or process used to remove heat from something or keep it at a lower temperature.
-
E.
hasCoolingCore
Indicates that an entity possesses a central region or core characterized by cooling or lower temperature relative to its surroundings.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 10:43 a.m.