Triple
T7199368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratified Flows |
E168699
|
entity |
| Predicate | includesMethod |
P33646
|
FINISHED |
| Object | linear stability analysis |
—
|
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: linear stability analysis | Statement: [Stratified Flows, includesMethod, linear stability analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMethod Context triple: [Stratified Flows, includesMethod, linear stability analysis]
-
A.
usesMethods
chosen
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
B.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
C.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
D.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
-
E.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92b8bc08190bfcdd34ce42e3448 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.