Triple
T34302595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baum–Welch algorithm |
E880219
|
entity |
| Predicate | M-stepUpdates |
P132547
|
FINISHED |
| Object | transition probabilities |
—
|
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: transition probabilities | Statement: [Baum–Welch algorithm, M-stepUpdates, transition probabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: M-stepUpdates Context triple: [Baum–Welch algorithm, M-stepUpdates, transition probabilities]
-
A.
multivariateUpdateFormula
Indicates a rule or expression that specifies how multiple variables are jointly updated or recalculated in relation to one another.
-
B.
stepUpdateType
Indicates the type or category of update applied to a particular step within a process or workflow.
-
C.
stepOfModel
chosen
Indicates that something is a specific step or stage within a larger model or process.
-
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.
highestMajorStep
Indicates the relationship where one entity represents the largest or most advanced major step, stage, or level reached or associated with 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.