Triple
T19582714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Discovery Protocol |
E490035
|
entity |
| Predicate | defaultStatusOnCiscoDevices |
P85920
|
FINISHED |
| Object | enabled |
—
|
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: enabled | Statement: [Cisco Discovery Protocol, defaultStatusOnCiscoDevices, enabled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultStatusOnCiscoDevices Context triple: [Cisco Discovery Protocol, defaultStatusOnCiscoDevices, enabled]
-
A.
defaultStateOnSupportedDevices
chosen
Indicates whether the feature or setting is turned on by default for devices that support it.
-
B.
networkDevice
Indicates that one entity functions as a network device that connects, routes, or manages data traffic between other entities in a network.
-
C.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
D.
CISStatus
Indicates the compliance or certification status of an entity with respect to CIS (Center for Internet Security) benchmarks or standards.
-
E.
adminStatus
Indicates that an entity holds an administrative role, privilege level, or state within a system or context.
- 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.