Triple

T11100579
Position Surface form Disambiguated ID Type / Status
Subject Crusoe microprocessor E262490 entity
Predicate executionCoreType P97284 FINISHED
Object in-order VLIW core 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: in-order VLIW core | Statement: [Crusoe microprocessor, executionCoreType, in-order VLIW core]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: executionCoreType
Context triple: [Crusoe microprocessor, executionCoreType, in-order VLIW core]
  • A. executionEngine
    Indicates the mechanism or component responsible for carrying out, managing, or running a defined process, task, or set of operations.
  • B. executionDomain
    Indicates the context, environment, or scope within which an action, process, or operation is carried out or valid.
  • C. executionModel
    Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
  • D. executionSide
    Indicates which party or side in a transaction, contract, or interaction is responsible for performing or carrying out the specified action.
  • E. executionDevice
    Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
  • 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_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.
PDg Predicate description generation batch_69d750ca52ec8190a559432a5de106fd completed April 9, 2026, 7:10 a.m.
Created at: April 8, 2026, 9:27 p.m.