Triple
T27638752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning Network |
E696533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | second-layer protocol |
C53076
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: second-layer protocol Context triple: [Lightning Network, instanceOf, second-layer protocol]
-
A.
session layer protocol
A session layer protocol is a network communication protocol that establishes, manages, and terminates logical connections (sessions) between applications, handling dialog control, synchronization, and orderly data exchange.
-
B.
transport layer protocol
A transport layer protocol is a communication protocol that provides end-to-end data transfer services between applications across networked devices, handling functions like segmentation, reliability, flow control, and multiplexing.
-
C.
network layer protocol
A network layer protocol defines the rules and mechanisms for routing and forwarding data packets across interconnected networks, providing logical addressing and path selection between source and destination hosts.
-
D.
link-layer protocol
A link-layer protocol defines the rules and procedures for reliable data transfer, framing, addressing, and error handling between directly connected network devices on a physical medium.
-
E.
packet-switched protocol
A packet-switched protocol is a communication method that breaks data into discrete packets, routes them independently across a network, and reassembles them at the destination for efficient and robust data transfer.
- F. None of above. chosen
Provenance (1 batch)
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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:25 p.m.