Triple
T27662203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gsutil |
E697149
|
entity |
| Predicate | typicalSubcommand |
P101150
|
FINISHED |
| Object | gsutil cp |
—
|
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: gsutil cp | Statement: [gsutil, typicalSubcommand, gsutil cp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubcommand Context triple: [gsutil, typicalSubcommand, gsutil cp]
-
A.
typicalCommands
Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
-
B.
typicalCommandLine
chosen
Indicates that one entity represents the usual or standard command-line invocation or syntax associated with another entity.
-
C.
typicalCommandLevel
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
D.
typicalCommandRank
Indicates the usual or most common rank at which an individual typically holds command authority in a given context.
-
E.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: April 27, 2026, 2:37 p.m.