Triple
T7086835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel AVX2 |
E165095
|
entity |
| Predicate | featureFlag |
P74449
|
FINISHED |
| Object | AVX2 CPUID bit |
—
|
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: AVX2 CPUID bit | Statement: [Intel AVX2, featureFlag, AVX2 CPUID bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureFlag Context triple: [Intel AVX2, featureFlag, AVX2 CPUID bit]
-
A.
featuresExperiment
Indicates that an entity is involved in, or is the subject of, a specific experimental setup, test, or trial.
-
B.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
C.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
D.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
E.
featuresService
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e513d9b08190a8a8d213c2264ce4 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:41 p.m.