Triple
T12373107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratonovich integral |
E295051
|
entity |
| Predicate | typicalIntegrand |
P94170
|
FINISHED |
| Object | adapted stochastic process |
—
|
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: adapted stochastic process | Statement: [Stratonovich integral, typicalIntegrand, adapted stochastic process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIntegrand Context triple: [Stratonovich integral, typicalIntegrand, adapted stochastic process]
-
A.
integrandFeature
chosen
Indicates that a specific mathematical feature or property is part of, or characterizes, the integrand in an integration expression or operation.
-
B.
integralTo
Indicates that one entity is an essential, non-removable component or part of another entity, such that the whole depends on it to function or be complete.
-
C.
integratesOn
Indicates that one entity is designed to work seamlessly within, or be combined functionally with, another entity or platform.
-
D.
integratedOver
Indicates that a quantity or function has been mathematically integrated with respect to a specified variable or domain over a given interval or region.
-
E.
integralVersionUsedIn
Indicates that a specific integral version (e.g., of a component, document, or artifact) is utilized within or by another entity or process.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.