Triple

T33660539
Position Surface form Disambiguated ID Type / Status
Subject Rankine cycle E862337 entity
Predicate hasHeatRejection P193674 FINISHED
Object heat rejected in 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: heat rejected in condenser | Statement: [Rankine cycle, hasHeatRejection, heat rejected in condenser]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHeatRejection
Context triple: [Rankine cycle, hasHeatRejection, heat rejected in condenser]
  • A. reducedEngineHeatComparedTo
    Indicates that one entity produces or exhibits a lower level of engine heat than another entity used as a point of comparison.
  • B. coolingSystemFeatures
    Indicates that one entity specifies or provides particular characteristics, components, or capabilities of a cooling system associated with another entity.
  • C. hasAirCooling
    Indicates that an entity is equipped with or utilizes an air-based cooling system.
  • D. hasCoolingCore
    Indicates that an entity possesses a central region or core characterized by cooling or lower temperature relative to its surroundings.
  • E. 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.
  • 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_69f34984c4008190bb82f33a7819da64 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd4f39b5008190b83b3227ce22c509 completed May 8, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69fd4df17c548190a4e2a6fea70f7e10 completed May 8, 2026, 2:44 a.m.
PDg Predicate description generation batch_69fd4f38728c8190b3271abc80882cfb completed May 8, 2026, 2:49 a.m.
Created at: May 1, 2026, 1:42 a.m.