Triple
T37074948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnot engine |
E917683
|
entity |
| Predicate | hasColdReservoirTemperatureSymbol |
P29590
|
FINISHED |
| Object | Tc |
—
|
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: Tc | Statement: [Carnot engine, hasColdReservoirTemperatureSymbol, Tc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColdReservoirTemperatureSymbol Context triple: [Carnot engine, hasColdReservoirTemperatureSymbol, Tc]
-
A.
symbolOfTemperature
chosen
Indicates that one entity serves as a symbolic representation or notation used to express the temperature of another entity.
-
B.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
C.
isCryogenic
Indicates that something operates at, is designed for, or involves extremely low (cryogenic) temperatures.
-
D.
hasTemperatureQualifier
Indicates that a temperature value is associated with a specific qualifier (such as approximate, minimum, maximum, or range) that refines or constrains its meaning.
-
E.
reservoirTemperature
Indicates the temperature value measured or assigned to a reservoir in the context of the described system or process.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.