Triple
T28610091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubuntu Pro |
E724147
|
entity |
| Predicate | securityCoverage |
P173723
|
FINISHED |
| Object | main repository packages |
—
|
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: main repository packages | Statement: [Ubuntu Pro, securityCoverage, main repository packages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCoverage Context triple: [Ubuntu Pro, securityCoverage, main repository packages]
-
A.
securityTypeCoverage
Indicates the type or category of security that is covered or included under a given coverage or policy.
-
B.
securityCapitalizationCoverage
Indicates the extent to which a security’s market capitalization is represented, included, or covered within a given dataset, index, or analytical scope.
-
C.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
D.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
E.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 28, 2026, 4:29 a.m.