Triple
T24014387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reynolds-averaged Navier–Stokes turbulence modeling |
E594627
|
entity |
| Predicate | typicallySolvesFor |
P8791
|
FINISHED |
| Object | mean velocity field |
—
|
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: mean velocity field | Statement: [Reynolds-averaged Navier–Stokes turbulence modeling, typicallySolvesFor, mean velocity field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallySolvesFor Context triple: [Reynolds-averaged Navier–Stokes turbulence modeling, typicallySolvesFor, mean velocity field]
-
A.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with another entity.
-
B.
commonlySolvedBy
chosen
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
C.
solutionDeterminedBy
Indicates that the value or outcome of a solution is fully specified or fixed by the referenced factor(s) or condition(s).
-
D.
requiresSolvingAlgebraicEquations
Indicates that performing or completing an action depends on solving algebraic equations.
-
E.
basedOnSolutionOf
Indicates that one entity is derived, developed, or constructed using the solution or outcome produced by another entity.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a0aa408190a27fca07777cda05 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.