Triple
T18723686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markov localization |
E457843
|
entity |
| Predicate | updateStep |
P6360
|
FINISHED |
| Object | prediction step using motion model |
—
|
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: prediction step using motion model | Statement: [Markov localization, updateStep, prediction step using motion model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateStep Context triple: [Markov localization, updateStep, prediction step using motion model]
-
A.
stepUpdateType
Indicates the type or category of update applied to a particular step within a process or workflow.
-
B.
updateProcess
chosen
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
C.
stepOfModel
Indicates that something is a specific step or stage within a larger model or process.
-
D.
administrationStep
Indicates a specific phase or stage within a broader administrative or management process.
-
E.
updateFor
Indicates that one entity is modified or refreshed in response to changes or conditions 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56abcfc048190a01dee959e768768 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.