Triple
T17677501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OTP |
E440676
|
entity |
| Predicate | developedForLanguage |
P75919
|
FINISHED |
| Object | Erlang |
—
|
NE NERFINISHED |
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: Erlang | Statement: [OTP, developedForLanguage, Erlang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Erlang Context triple: [OTP, developedForLanguage, Erlang]
-
A.
Erlang
chosen
Erlang is a functional, concurrent programming language designed for building highly scalable, fault-tolerant distributed systems, originally developed by Ericsson for telecom applications.
-
B.
Elixir
Elixir is a functional, concurrent programming language built on the Erlang VM, known for its scalability, fault tolerance, and expressive syntax.
-
C.
Erlang VM
The Erlang VM (BEAM) is a highly concurrent, fault-tolerant virtual machine designed for building scalable, distributed systems and real-time applications.
-
D.
Programming Erlang
Programming Erlang is a foundational book by Joe Armstrong that introduces and explains the Erlang programming language, particularly its strengths in concurrency, fault tolerance, and distributed systems.
-
E.
Erlang/OTP team
The Erlang/OTP team is the group at Ericsson responsible for developing and maintaining the Erlang programming language and its Open Telecom Platform (OTP) libraries and runtime system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 10:01 a.m.