Triple
T33027670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKD |
E845084
|
entity |
| Predicate | commandChannel |
P2798
|
FINISHED |
| Object | FTP control connection |
—
|
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 control connection | Statement: [MKD, commandChannel, FTP control connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandChannel Context triple: [MKD, commandChannel, FTP control connection]
-
A.
coreChannel
Indicates a primary or central communication channel through which key information, signals, or interactions are transmitted.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
centralCommand
Indicates that one entity serves as the primary controlling or coordinating authority over the operations, decisions, or activities of another entity or group.
-
E.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:23 a.m.