Triple
T4600154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenBSD |
E100302
|
entity |
| Predicate | packageManagement |
P5091
|
FINISHED |
| Object | pkg_add |
—
|
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: pkg_add | Statement: [OpenBSD, packageManagement, pkg_add]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packageManagement Context triple: [OpenBSD, packageManagement, pkg_add]
-
A.
packageManager
chosen
Indicates that a software package is managed, installed, or maintained by a specific package management system.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
D.
programManaged
Indicates that one entity is responsible for overseeing, organizing, or administering a program associated with another entity.
-
E.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5971f448819090f6e76c7d3ffc2d |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.