Triple
T28506693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian backports |
E721380
|
entity |
| Predicate | securitySupportScope |
P105186
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Debian backports, securitySupportScope, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securitySupportScope Context triple: [Debian backports, securitySupportScope, limited]
-
A.
securityScope
Indicates the range or extent of protection, permissions, or access control that applies within a given security context.
-
B.
securityDependence
Indicates a relationship where one entity relies on another to ensure its safety, protection, or defense from threats.
-
C.
securityBasisFor
Indicates that one entity serves as the justification, foundation, or underlying reason for the security of another entity.
-
D.
securityContext
Indicates the security-related settings or constraints under which an action, process, or interaction is performed.
-
E.
guaranteeScope
chosen
Indicates that one entity defines or limits the extent, conditions, or coverage under which a guarantee provided by another entity is valid.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 3:09 a.m.