Triple

T17674864
Position Surface form Disambiguated ID Type / Status
Subject BEAM virtual machine E440619 entity
Predicate implements P1417 FINISHED
Object Erlang distribution protocol — NE NERFINISHED

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: Erlang distribution protocol | Statement: [BEAM virtual machine, implements, Erlang distribution protocol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Erlang distribution protocol
Context triple: [BEAM virtual machine, implements, Erlang distribution protocol]
  • A. Erlang
    Erlang is a functional, concurrent programming language designed for building highly scalable, fault-tolerant distributed systems, originally developed by Ericsson for telecom applications.
  • B. Erlang VM
    The Erlang VM (BEAM) is a highly concurrent, fault-tolerant virtual machine designed for building scalable, distributed systems and real-time applications.
  • C. Distributed Network Protocol
    Distributed Network Protocol is a communications protocol widely used in electric and water utilities for reliable, secure, and time-synchronized data exchange between control systems and remote devices.
  • D. Echo Protocol
    Echo Protocol is a simple network service defined in RFC 862 that sends back any data it receives, primarily used for testing and diagnostic purposes.
  • E. Annex E (Distributed Systems)
    Annex E (Distributed Systems) is an Ada language annex that defines standardized features for building and managing distributed systems, including partitioning, remote subprogram calls, and inter-partition communication.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Erlang distribution protocol
Target entity description: The Erlang distribution protocol is the communication mechanism that enables Erlang (and Elixir) nodes to connect, authenticate, and exchange messages transparently across a distributed system.
  • A. Erlang
    Erlang is a functional, concurrent programming language designed for building highly scalable, fault-tolerant distributed systems, originally developed by Ericsson for telecom applications.
  • B. Erlang VM
    The Erlang VM (BEAM) is a highly concurrent, fault-tolerant virtual machine designed for building scalable, distributed systems and real-time applications.
  • C. Distributed Network Protocol
    Distributed Network Protocol is a communications protocol widely used in electric and water utilities for reliable, secure, and time-synchronized data exchange between control systems and remote devices.
  • D. Echo Protocol
    Echo Protocol is a simple network service defined in RFC 862 that sends back any data it receives, primarily used for testing and diagnostic purposes.
  • E. Annex E (Distributed Systems)
    Annex E (Distributed Systems) is an Ada language annex that defines standardized features for building and managing distributed systems, including partitioning, remote subprogram calls, and inter-partition communication.
  • F. None of above. chosen

Provenance (2 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6ba22081909e2099490c047378 completed April 19, 2026, 6 a.m.
Created at: April 10, 2026, 10 a.m.