Triple
T31583844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse MV/8000 |
E805894
|
entity |
| Predicate | instructionExecution |
P155185
|
FINISHED |
| Object | microcode-controlled |
—
|
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: microcode-controlled | Statement: [Eclipse MV/8000, instructionExecution, microcode-controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionExecution Context triple: [Eclipse MV/8000, instructionExecution, microcode-controlled]
-
A.
instructionIssue
Indicates that one entity issues or gives an instruction or directive to another entity.
-
B.
instructionLevel
Indicates the degree or stage of guidance, teaching, or educational complexity associated with an action or relationship.
-
C.
instructionMode
Indicates the method or medium through which an instruction, lesson, or teaching activity is delivered.
-
D.
instructionMnemonic
Indicates that one entity is the mnemonic name or shorthand representation used to denote a particular instruction in an instruction set or language.
-
E.
executionDescription
chosen
Indicates the specific manner, details, or narrative of how an execution (of a process, action, or event) is or was carried out.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:24 p.m.