Triple

T27638778
Position Surface form Disambiguated ID Type / Status
Subject Lightning Network E696533 entity
Predicate hasRoutingProtocol P31502 FINISHED
Object BOLT 4
BOLT 4 is a specification document that defines the onion-style packet format and routing protocol used to relay payments across the Bitcoin Lightning Network.
 E1783637 NE FINISHED

How this triple was built (3 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: BOLT 4 | Statement: [Lightning Network, hasRoutingProtocol, BOLT 4]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: BOLT 4
Triple: [Lightning Network, hasRoutingProtocol, BOLT 4]
Generated description
BOLT 4 is a specification document that defines the onion-style packet format and routing protocol used to relay payments across the Bitcoin Lightning Network.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: hasRoutingProtocol
Context triple: [Lightning Network, hasRoutingProtocol, BOLT 4]
  • A. routingProtocol chosen
    Indicates that one entity uses, implements, or is associated with a specific routing protocol to determine paths for forwarding data in a network.
  • B. supportsHierarchicalRouting
    Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
  • C. hasRouteNetwork
    Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
  • D. supportsClasslessRouting
    Indicates that an entity is capable of handling routing without relying on classful IP address boundaries, typically using subnet masks or CIDR for route determination.
  • E. routingCapability
    Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
  • F. None of above.

Provenance (6 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_69ef5909f3848190805f35b76833e722 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a12da8d4a3c8190a5d96dddf2d26972 completed May 24, 2026, 11:01 a.m.
NEDg Description generation batch_6a12dbdc81948190b273567639a905cd completed May 24, 2026, 11:07 a.m.
NED2 Entity disambiguation (via description) batch_6a12dc453c5c819094d51c46c94b5905 completed May 24, 2026, 11:08 a.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
Created at: April 27, 2026, 2:25 p.m.