Triple
T7803618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fischer esterification |
E180491
|
entity |
| Predicate | equilibriumControlled |
P79102
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fischer esterification, equilibriumControlled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equilibriumControlled Context triple: [Fischer esterification, equilibriumControlled, true]
-
A.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
B.
oppositeControlledBy
Indicates that one entity is under the control or influence of another entity that is positioned or defined as its opposite or counterpart.
-
C.
equilibriumFigure
Indicates a stable configuration or shape in which all acting forces or influences on an object or system are balanced.
-
D.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
E.
controlledChamber
Indicates that an entity has authority over, manages, or directs the operations or decisions of a particular chamber or deliberative body.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:34 p.m.