Triple
T20186069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link Layer Topology Discovery |
E492864
|
entity |
| Predicate | frameDestinationAddress |
P139024
|
FINISHED |
| Object | 01:80:C2:00:00:0E |
—
|
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:80:C2:00:00:0E | Statement: [Link Layer Topology Discovery, frameDestinationAddress, 01:80:C2:00:00:0E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameDestinationAddress Context triple: [Link Layer Topology Discovery, frameDestinationAddress, 01:80:C2:00:00:0E]
-
A.
typicalDestinationAddress
Indicates the address that is most commonly or usually used as the destination for something or someone.
-
B.
frame
Indicates placing or presenting something within a particular context, structure, or perspective that shapes how it is interpreted.
-
C.
sampleDestination
Indicates that something serves as, or is designated to be, the target location or endpoint for a sample.
-
D.
frameDevice
Indicates that one entity serves as a structural or supporting frame for another device or object.
-
E.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
- F. None of above. chosen
Provenance (4 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668f2c03c819096336462f59dba91 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:36 p.m.