Triple
T25425317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel MPX |
E637101
|
entity |
| Predicate | checkingType |
P158291
|
FINISHED |
| Object | spatial memory bounds checking |
—
|
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: spatial memory bounds checking | Statement: [Intel MPX, checkingType, spatial memory bounds checking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkingType Context triple: [Intel MPX, checkingType, spatial memory bounds checking]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
matchesType
Indicates that one entity has the same or a compatible type as another entity according to a defined type system or classification.
-
C.
seeType
Indicates that one entity observes, recognizes, or visually perceives another entity of a particular type or category.
-
D.
testType
Indicates the specific category or kind of test associated with an entity or event.
-
E.
isNotType
Indicates that one entity is explicitly not of a specified type or category in relation to another.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:57 p.m.