Triple
T2092825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stokes flow |
E32707
|
entity |
| Predicate | hasApproximation |
P4447
|
FINISHED |
| Object | Oseen approximation for slightly higher Reynolds numbers |
—
|
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: Oseen approximation for slightly higher Reynolds numbers | Statement: [Stokes flow, hasApproximation, Oseen approximation for slightly higher Reynolds numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximation Context triple: [Stokes flow, hasApproximation, Oseen approximation for slightly higher Reynolds numbers]
-
A.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
approximationType
chosen
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
D.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
E.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.