Triple
T32377574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Pentium Gold 4415Y |
E827330
|
entity |
| Predicate | supportsInTru3D |
P206261
|
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 Pentium Gold 4415Y, supportsInTru3D, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInTru3D Context triple: [Intel Pentium Gold 4415Y, supportsInTru3D, yes]
-
A.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
-
B.
has3DVersion
Indicates that an entity has a corresponding three-dimensional (3D) version or representation.
-
C.
supports3DPerspective
Indicates that one entity provides or enables three-dimensional perspective viewing or rendering capabilities for another.
-
D.
has3DGraphics
Indicates that something includes or supports three-dimensional graphical representation or rendering.
-
E.
supports3DAcceleration
Indicates that one entity provides or enables hardware- or software-based 3D graphics acceleration for another entity.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:51 a.m.