Triple
T11100567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusoe microprocessor |
E262490
|
entity |
| Predicate | instructionTranslationLayer |
P97283
|
FINISHED |
| Object | stored in flash memory |
—
|
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: stored in flash memory | Statement: [Crusoe microprocessor, instructionTranslationLayer, stored in flash memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionTranslationLayer Context triple: [Crusoe microprocessor, instructionTranslationLayer, stored in flash memory]
-
A.
instructionLevel
Indicates the degree or stage of guidance, teaching, or educational complexity associated with an action or relationship.
-
B.
instructionMode
Indicates the method or medium through which an instruction, lesson, or teaching activity is delivered.
-
C.
translationHint
Indicates that one entity provides guidance or suggestions on how another entity should be translated into a different language.
-
D.
inscriptionTranslation
Indicates that a provided text expresses the translated content of a specific inscription.
-
E.
translationActivity
Indicates that an entity is engaged in the process of translating content from one language or form into another.
- 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.