Triple
T37074950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnot engine |
E917683
|
entity |
| Predicate | efficiencyLessThanOrEqualTo |
P64354
|
FINISHED |
| Object | 1 - Tc/Th for any real engine |
—
|
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: 1 - Tc/Th for any real engine | Statement: [Carnot engine, efficiencyLessThanOrEqualTo, 1 - Tc/Th for any real engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: efficiencyLessThanOrEqualTo Context triple: [Carnot engine, efficiencyLessThanOrEqualTo, 1 - Tc/Th for any real engine]
-
A.
lessThanOrEqualTo
chosen
Indicates that one entity’s value is smaller than or exactly equal to another entity’s value.
-
B.
isLessEfficientThan
Indicates that one entity performs a task or uses resources with lower efficiency compared to another entity.
-
C.
hasEfficiencyMetric
Indicates that an entity is associated with a specific measure or metric used to evaluate its efficiency.
-
D.
hasLowerThroughputThan
Indicates that one entity’s throughput is less than that of another entity.
-
E.
hasMaximumEfficiencyAt
Indicates that an entity reaches or exhibits its highest possible efficiency under a specified condition, context, or parameter value.
- 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_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.