Triple
T7387512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 4001 |
E170417
|
entity |
| Predicate | instructionStorage |
P69226
|
FINISHED |
| Object | stores 4004 instruction code |
—
|
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: stores 4004 instruction code | Statement: [Intel 4001, instructionStorage, stores 4004 instruction code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionStorage Context triple: [Intel 4001, instructionStorage, stores 4004 instruction code]
-
A.
instruction
Indicates that one entity provides a directive or order specifying an action that another entity should perform.
-
B.
includesInstruction
chosen
Indicates that one entity contains, provides, or embeds an instruction or set of instructions directed toward another entity.
-
C.
usageInstruction
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle another entity.
-
D.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
E.
instructionBegan
Indicates that an instructional process or teaching activity has started.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f2bac481908ac74069182a4ce4 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.