Triple
T12703511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clausius–Clapeyron relation |
E303520
|
entity |
| Predicate | approximateForm |
P4460
|
FINISHED |
| Object | ln(P) = −L∕(R·T) + constant |
—
|
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: ln(P) = −L∕(R·T) + constant | Statement: [Clausius–Clapeyron relation, approximateForm, ln(P) = −L∕(R·T) + constant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateForm Context triple: [Clausius–Clapeyron relation, approximateForm, ln(P) = −L∕(R·T) + constant]
-
A.
approximates
chosen
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
B.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
C.
generalizedForm
Indicates that one entity is a more abstract, generalized version or broader form of another entity.
-
D.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
E.
formsNear
Indicates that one entity takes shape or comes into existence in close spatial proximity to another entity.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.