Triple
T26034691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hele–Shaw cell |
E647519
|
entity |
| Predicate | typicalFlowRegime |
P8240
|
FINISHED |
| Object | low Reynolds number |
—
|
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: low Reynolds number | Statement: [Hele–Shaw cell, typicalFlowRegime, low Reynolds number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlowRegime Context triple: [Hele–Shaw cell, typicalFlowRegime, low Reynolds number]
-
A.
hasFlowRegime
chosen
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
B.
ReynoldsNumberCapability
Indicates the ability or suitability of a system or context to be characterized, analyzed, or operated in terms of Reynolds number–based flow behavior.
-
C.
regulatesFlowBetween
Indicates a relationship where one entity controls, directs, or modulates the movement or transfer of something (such as material, energy, or information) between two other entities.
-
D.
flowSpeed
Indicates the rate at which a fluid or medium moves through a given point or along a path over time.
-
E.
regulatesFlowFor
Indicates that one entity controls, directs, or manages the rate or movement of another entity’s flow.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 22, 2026, 9:07 a.m.