Triple
T7857878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft HoloLens |
E182421
|
entity |
| Predicate | processor |
P8608
|
FINISHED |
| Object | custom holographic processing unit |
—
|
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: custom holographic processing unit | Statement: [Microsoft HoloLens, processor, custom holographic processing unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processor Context triple: [Microsoft HoloLens, processor, custom holographic processing unit]
-
A.
cpu
chosen
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
B.
microarchitectureClass
Indicates that one entity is classified as a specific type or category of microarchitecture relative to another entity.
-
C.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
D.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
E.
microarchitectureFeature
Indicates a relationship where a specific microarchitecture possesses or supports a particular hardware or design feature.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.