Triple
T38211279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmholtz free energy |
E1010551
|
entity |
| Predicate | naturalVariable |
P107623
|
FINISHED |
| Object | temperature |
—
|
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: temperature | Statement: [Helmholtz free energy, naturalVariable, temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalVariable Context triple: [Helmholtz free energy, naturalVariable, temperature]
-
A.
naturalVariables
chosen
Indicates that certain variables or parameters arise directly from the inherent properties or natural behavior of a system, rather than being externally imposed or artificially defined.
-
B.
naturalSetting
Indicates that something is located in, occurs within, or is characterized by a natural, non-artificial environment or surroundings.
-
C.
naturalOrArtificial
Indicates that something is classified as either naturally occurring or artificially created.
-
D.
naturalDomain
Indicates that something inherently belongs to or operates within a particular domain, scope, or area of applicability.
-
E.
usesVAR
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.