Triple
T11100551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusoe microprocessor |
E262490
|
entity |
| Predicate | underlyingInstructionSet |
P78644
|
FINISHED |
| Object | proprietary VLIW instruction set |
—
|
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: proprietary VLIW instruction set | Statement: [Crusoe microprocessor, underlyingInstructionSet, proprietary VLIW instruction set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingInstructionSet Context triple: [Crusoe microprocessor, underlyingInstructionSet, proprietary VLIW instruction set]
-
A.
instructionSetType
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
B.
hasInstructionSet
chosen
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
C.
instructionSetSize
Indicates the size or number of instructions defined in an instruction set.
-
D.
instructionSetExtensions
Indicates that one entity defines, supports, or includes additional instruction set features or extensions relative to another.
-
E.
instructionSetExtension
Indicates that one instruction set architecture extends or augments another with additional instructions or capabilities.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a29ee6c819092bc0da3f9255389 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.