Triple
T8052815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core i3-10100Y |
E187714
|
entity |
| Predicate | supportsIntelVT-xWithEPT |
P80764
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Intel Core i3-10100Y, supportsIntelVT-xWithEPT, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntelVT-xWithEPT Context triple: [Intel Core i3-10100Y, supportsIntelVT-xWithEPT, yes]
-
A.
supportsNestedVirtualization
Indicates that one computing environment or platform enables and correctly handles running virtual machines inside other virtual machines.
-
B.
supportsBigLittleHybrid
Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
-
C.
virtualizationType
Indicates the specific method or technology by which a resource, system, or environment is virtualized.
-
D.
supportsPCIeVersion
Indicates that one entity is compatible with or able to operate using a specified version of the PCI Express (PCIe) standard.
-
E.
firstSupportedMicroarchitecture
Indicates the earliest or oldest microarchitecture that provides support for a given hardware or software feature.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7c425c8190aa1b2f534afeb58c |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:25 p.m.