Triple
T11751673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPMI |
E279419
|
entity |
| Predicate | targetProcessorMode |
P97361
|
FINISHED |
| Object | x86 protected mode |
—
|
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: x86 protected mode | Statement: [DPMI, targetProcessorMode, x86 protected mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetProcessorMode Context triple: [DPMI, targetProcessorMode, x86 protected mode]
-
A.
usesProcessorSeries
Indicates that one entity operates using, or is built to run on, a specific series or family of processors.
-
B.
targetFeature
chosen
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
-
C.
introducedByProcessor
Indicates that something was created, added, or brought into a system as a result of actions performed by a specific processor.
-
D.
mainProcessor
Indicates that an entity serves as the primary or central processing unit responsible for executing core operations or computations for another entity or system.
-
E.
builtInProcessor
Indicates that one entity serves as an internal or integrated processing unit within another entity.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a509c2448190b0deb7ed29c3a73f |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.