Triple
T21012146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibbs phase rule |
E517574
|
entity |
| Predicate | condensedFormAppliesTo |
P23250
|
FINISHED |
| Object | systems at constant pressure |
—
|
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: systems at constant pressure | Statement: [Gibbs phase rule, condensedFormAppliesTo, systems at constant pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: condensedFormAppliesTo Context triple: [Gibbs phase rule, condensedFormAppliesTo, systems at constant pressure]
-
A.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
B.
adoptedInForm
Indicates that something is accepted, implemented, or brought into use within a particular form, format, or structural arrangement.
-
C.
standardFormUsedIn
chosen
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
D.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
hasConjunctForms
Indicates that an entity is associated with one or more conjunct (combined or compound) forms of itself or related elements.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc40f91c81908c9b6d99869de7aa |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.