Triple
T33027531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TYPE |
E845080
|
entity |
| Predicate | hasCommandClass |
—
|
GENERATED |
| Object | FTP service command |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommandClass Context triple: [TYPE, hasCommandClass, FTP service command]
-
A.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
B.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
C.
hasCommandSystem
Indicates that one entity possesses, uses, or is associated with a particular command or control system.
-
D.
hasCommunicationClass
Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
-
E.
hasCommandResponsibilityFor
Indicates that one entity holds authoritative control over, and is responsible for directing and overseeing, the actions or operations of another entity.
- F. None of above. chosen
Provenance (1 batch)
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.