Triple
T14160418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayleigh–Bénard convection |
E350921
|
entity |
| Predicate | onsetCondition |
P9036
|
FINISHED |
| Object | Rayleigh number exceeds critical value |
—
|
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: Rayleigh number exceeds critical value | Statement: [Rayleigh–Bénard convection, onsetCondition, Rayleigh number exceeds critical value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onsetCondition Context triple: [Rayleigh–Bénard convection, onsetCondition, Rayleigh number exceeds critical value]
-
A.
hasOnset
chosen
Indicates the point in time or condition at which a process, event, or state begins.
-
B.
onsetRate
Indicates the rate at which an event, condition, or process begins or develops over time.
-
C.
hasOnsetTypes
Indicates the types or categories of onset (e.g., how or when something begins) that are associated with a given entity or condition.
-
D.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61393f308190bb357e2bd1916f94 |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.