Triple
T33660507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rankine cycle |
E862337
|
entity |
| Predicate | hasWorkingFluid |
P56023
|
FINISHED |
| Object | water |
—
|
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: water | Statement: [Rankine cycle, hasWorkingFluid, water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingFluid Context triple: [Rankine cycle, hasWorkingFluid, water]
-
A.
usesWorkingFluid
chosen
Indicates that one entity operates or functions by employing another entity as its working fluid.
-
B.
hasFluid
Indicates that one entity contains, holds, or is associated with a particular fluid.
-
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.
hasHydraulicFeature
Indicates that an entity possesses or includes a hydraulic element or system related to the movement, control, or use of fluids.
-
E.
hasFillingSystem
Indicates that an entity is equipped with or uses a particular filling system or mechanism.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 1, 2026, 1:42 a.m.