Triple
T19582737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Discovery Protocol |
E490035
|
entity |
| Predicate | usesMulticastMACAddress |
P23645
|
FINISHED |
| Object | 01:00:0C:CC:CC:CC |
—
|
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: 01:00:0C:CC:CC:CC | Statement: [Cisco Discovery Protocol, usesMulticastMACAddress, 01:00:0C:CC:CC:CC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMulticastMACAddress Context triple: [Cisco Discovery Protocol, usesMulticastMACAddress, 01:00:0C:CC:CC:CC]
-
A.
usesMulticastAddress
chosen
Indicates that one entity communicates or operates using a multicast network address to reach multiple recipients simultaneously.
-
B.
supportsMulticast
Indicates that an entity is capable of handling or enabling multicast communication, where data is transmitted from one sender to multiple receivers simultaneously.
-
C.
canBeUnicast
Indicates that the subject is capable of being transmitted or addressed as a unicast, i.e., sent directly from one sender to a single specific receiver.
-
D.
learnsMACAddressesFrom
Indicates that one entity discovers or acquires knowledge of MAC addresses from another entity.
-
E.
hasMultiplexedAddressDataBus
Indicates that the address and data signals share the same physical bus lines, being transmitted at different times rather than on separate dedicated buses.
- 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.