Triple
T249269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navier–Stokes equations |
E5106
|
entity |
| Predicate | unknownsInclude |
P1393
|
FINISHED |
| Object | 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: velocity field | Statement: [Navier–Stokes equations, unknownsInclude, velocity field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unknownsInclude Context triple: [Navier–Stokes equations, unknownsInclude, velocity field]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
C.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
D.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
E.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.