Triple
T28614395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PackageManagement |
E724241
|
entity |
| Predicate | exposesCommand |
P33029
|
FINISHED |
| Object | Find-Package |
—
|
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: Find-Package | Statement: [PackageManagement, exposesCommand, Find-Package]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesCommand Context triple: [PackageManagement, exposesCommand, Find-Package]
-
A.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
B.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
C.
givesCommand
Indicates that one entity issues an order or directive that another entity is expected to follow.
-
D.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
E.
componentCommand
chosen
Indicates that one entity issues or defines a command that is executed or interpreted by another component within a system.
- 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_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 4:31 a.m.