Triple
T7304723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSSE3 |
E167944
|
entity |
| Predicate | requiresFeatureFlag |
P29514
|
FINISHED |
| Object | SSSE3 CPUID feature 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: SSSE3 CPUID feature bit | Statement: [SSSE3, requiresFeatureFlag, SSSE3 CPUID feature bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFeatureFlag Context triple: [SSSE3, requiresFeatureFlag, SSSE3 CPUID feature bit]
-
A.
featureFlag
Indicates that a particular functionality or behavior is conditionally enabled or disabled for an entity based on a configurable flag.
-
B.
requiresCapability
chosen
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
E.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd61c0c8190abb1368c9dfb1550 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.