Triple
T1936239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homebrew |
E41448
|
entity |
| Predicate | supportsSubcommand |
P11061
|
FINISHED |
| Object | brew install |
—
|
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: brew install | Statement: [Homebrew, supportsSubcommand, brew install]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSubcommand Context triple: [Homebrew, supportsSubcommand, brew install]
-
A.
supportsCommand
chosen
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
B.
hasSubordinateCommand
Indicates that one command or unit holds authority over and directs the operations of another command or unit that is subordinate to it.
-
C.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
D.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c5f6e481909b2d95861e2098f9 |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.