Triple
T28505191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluma |
E721347
|
entity |
| Predicate | supportsCommandLineInvocation |
P79901
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pluma, supportsCommandLineInvocation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCommandLineInvocation Context triple: [Pluma, supportsCommandLineInvocation, true]
-
A.
hasCommandLineInterface
chosen
Indicates that an entity provides or supports interaction through a command-line interface (CLI).
-
B.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
C.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
D.
hasCommandSystem
Indicates that one entity possesses, uses, or is associated with a particular command or control system.
-
E.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: April 28, 2026, 3:09 a.m.