Triple
T28609351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StackGuard |
E724133
|
entity |
| Predicate | inserts |
P97652
|
FINISHED |
| Object | canary word between buffer and control data on stack |
—
|
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: canary word between buffer and control data on stack | Statement: [StackGuard, inserts, canary word between buffer and control data on stack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inserts Context triple: [StackGuard, inserts, canary word between buffer and control data on stack]
-
A.
insertedUnder
Indicates that one entity has been placed or positioned beneath another entity, typically in a physical or structural context.
-
B.
insertionManeuver
chosen
Indicates the action of placing or guiding one object or component into another or into a designated position.
-
C.
insertedBy
Indicates that one entity was placed, added, or introduced into another entity or context by a specific agent or process.
-
D.
joins
Indicates that one entity becomes a member or part of another entity, typically by entering into an organization, group, or association.
-
E.
inducts
Indicates formally bringing someone into a group, organization, office, or honor by an official or ceremonial process.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:29 a.m.