Triple
T25425320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel MPX |
E637101
|
entity |
| Predicate | supportStatusInLinux |
P160766
|
FINISHED |
| Object | removed from mainline Linux kernel |
—
|
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: removed from mainline Linux kernel | Statement: [Intel MPX, supportStatusInLinux, removed from mainline Linux kernel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportStatusInLinux Context triple: [Intel MPX, supportStatusInLinux, removed from mainline Linux kernel]
-
A.
vendorSupportStatus
chosen
Indicates the current level or state of support provided by a vendor for a product, service, or customer.
-
B.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
E.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 21, 2026, 1:57 p.m.