Triple
T25933286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DL Boost |
E653484
|
entity |
| Predicate | architectureLevel |
P164815
|
FINISHED |
| Object | x86 instruction set architecture extension |
—
|
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 instruction set architecture extension | Statement: [DL Boost, architectureLevel, x86 instruction set architecture extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectureLevel Context triple: [DL Boost, architectureLevel, x86 instruction set architecture extension]
-
A.
buildingLevels
Indicates the number of floors or levels that a building has.
-
B.
infrastructureLevel
Indicates the degree or quality of infrastructure present or provided in relation to an entity or location.
-
C.
frameworkLevel
Indicates the hierarchical or maturity level assigned to a particular framework within a defined system or context.
-
D.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
E.
level2Feature
Indicates that an entity possesses or is associated with a secondary or intermediate-level feature within a hierarchical feature structure.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 22, 2026, 8:37 a.m.