Triple
T19582744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Discovery Protocol |
E490035
|
entity |
| Predicate | showCommand |
P21357
|
FINISHED |
| Object | show cdp neighbors |
—
|
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: show cdp neighbors | Statement: [Cisco Discovery Protocol, showCommand, show cdp neighbors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showCommand Context triple: [Cisco Discovery Protocol, showCommand, show cdp neighbors]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
D.
givesCommand
Indicates that one entity issues an order or directive that another entity is expected to follow.
-
E.
associatedCommand
chosen
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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404e18f88190b7fec59499dd25e8 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.