Triple
T37074930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnot engine |
E917683
|
entity |
| Predicate | hasNetInternalEnergyChangeOverCycle |
P120462
|
FINISHED |
| Object | zero |
—
|
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: zero | Statement: [Carnot engine, hasNetInternalEnergyChangeOverCycle, zero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetInternalEnergyChangeOverCycle Context triple: [Carnot engine, hasNetInternalEnergyChangeOverCycle, zero]
-
A.
hasEntropyChangeOverCycle
Indicates that a system undergoes a net change in entropy over the course of a complete cycle.
-
B.
hasFuelCycleCapability
Indicates that an entity possesses the technical and operational ability to carry out one or more stages of the nuclear fuel cycle (such as fuel production, use, or reprocessing).
-
C.
energyChange
chosen
Indicates a change in the amount or state of energy associated with an entity or process, typically specifying how much energy is gained or lost.
-
D.
hasEnergyFunction
Indicates that an entity is associated with, governed by, or characterized through a specific energy function.
-
E.
hasEnergyInput
Indicates that an entity receives or requires a specified source or form of energy to operate or occur.
- 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_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:14 p.m.