Triple
T25436407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | x87 FPU |
E637383
|
entity |
| Predicate | hasInstructionSetPrefix |
P76105
|
FINISHED |
| Object | FPU instructions starting with F |
—
|
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: FPU instructions starting with F | Statement: [x87 FPU, hasInstructionSetPrefix, FPU instructions starting with F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstructionSetPrefix Context triple: [x87 FPU, hasInstructionSetPrefix, FPU instructions starting with F]
-
A.
hasInstructionPrefix
chosen
Indicates that one entity provides an initial segment or starting portion that serves as the instruction prefix for another entity.
-
B.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
C.
hasInstructionCache
Indicates that an entity possesses or is equipped with an instruction cache for storing and accessing executable instructions.
-
D.
instructionSetType
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
E.
instructionSetSize
Indicates the size or number of instructions defined in an instruction set.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 1:59 p.m.