Triple
T19582721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Discovery Protocol |
E490035
|
entity |
| Predicate | informationAdvertised |
P98094
|
FINISHED |
| Object | device ID |
—
|
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: device ID | Statement: [Cisco Discovery Protocol, informationAdvertised, device ID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationAdvertised Context triple: [Cisco Discovery Protocol, informationAdvertised, device ID]
-
A.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
B.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
C.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
-
D.
offersInformationOn
chosen
Indicates that one entity provides or makes available information about another entity or topic.
-
E.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity 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.