Triple
T12945575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibbs free energy |
E309752
|
entity |
| Predicate | standardStateSymbol |
P82723
|
FINISHED |
| Object | ΔG° |
—
|
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: ΔG° | Statement: [Gibbs free energy, standardStateSymbol, ΔG°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardStateSymbol Context triple: [Gibbs free energy, standardStateSymbol, ΔG°]
-
A.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
B.
symbolForState
chosen
Indicates that one entity serves as the symbolic representation (such as an icon, emblem, or notation) used to denote or stand for a particular state of another entity.
-
C.
statusSymbol
Indicates that something serves as a marker or representation of an entity’s social, economic, or cultural standing relative to others.
-
D.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
stateRock
Indicates that an entity is in a solid, rock-like physical state or condition.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.