Triple
T35169351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robbins–Monro algorithm |
E1015498
|
entity |
| Predicate | typicalStepSizeForm |
P96497
|
FINISHED |
| Object | a_n = c / n |
—
|
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: a_n = c / n | Statement: [Robbins–Monro algorithm, typicalStepSizeForm, a_n = c / n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStepSizeForm Context triple: [Robbins–Monro algorithm, typicalStepSizeForm, a_n = c / n]
-
A.
typicalStep
Indicates that an action, event, or sub-process is a standard or commonly occurring step within a larger process or procedure.
-
B.
stepType
Indicates the specific kind or category of step an entity represents within a process or sequence.
-
C.
stepSizeSymbol
chosen
Indicates the symbolic representation used to denote the size or magnitude of a step in a process, sequence, or operation.
-
D.
stepping
Indicates that an entity is moving its foot or feet to take a step, often as part of walking or changing position.
-
E.
stepQuality
Indicates the degree or standard of how well a particular step or stage in a process is performed or executed.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.