Triple
T33027531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TYPE |
E845080
|
entity |
| Predicate | hasCommandClass |
P206324
|
FINISHED |
| Object | FTP service command |
—
|
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: FTP service command | Statement: [TYPE, hasCommandClass, FTP service command]
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 (4 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:23 a.m.