Triple
T12945549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibbs free energy |
E309752
|
entity |
| Predicate | extensiveOrIntensive |
P107620
|
FINISHED |
| Object | extensive quantity |
—
|
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: extensive quantity | Statement: [Gibbs free energy, extensiveOrIntensive, extensive quantity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensiveOrIntensive Context triple: [Gibbs free energy, extensiveOrIntensive, extensive quantity]
-
A.
isIntense
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
B.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
C.
moreExpressiveThan
Indicates that one entity conveys ideas, emotions, or information with greater richness, nuance, or clarity than another.
-
D.
isComprehensive
Indicates that something fully covers all relevant aspects, elements, or details of a subject without significant omissions.
-
E.
isExpensive
Indicates that something has a high cost or price relative to typical or expected alternatives.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d97e5811f481908178fac6d2e0efcd |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 5:43 p.m.