Triple
T7150461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milstein method |
E166677
|
entity |
| Predicate | stepUpdateType |
P75143
|
FINISHED |
| Object | explicit update scheme |
—
|
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: explicit update scheme | Statement: [Milstein method, stepUpdateType, explicit update scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stepUpdateType Context triple: [Milstein method, stepUpdateType, explicit update scheme]
-
A.
stepTakes
Indicates that one step directly follows or is taken after another step in a process or sequence.
-
B.
stepReturns
Indicates that a particular step in a process or workflow yields, outputs, or hands back a specified result or value.
-
C.
stepRelative
Indicates a familial relationship where one person is a step-relative of another, such as a step-parent, step-child, or step-sibling, created through marriage rather than blood or adoption.
-
D.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
E.
upgradePhase
Indicates the stage or step within a process where an entity is being upgraded or transitioned to a more advanced version or state.
- F. None of above. chosen
Provenance (4 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f28b188190b1732ca711666531 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.