Triple
T17674937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix |
E440621
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | Erlang VM |
E440618
|
NE 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: Erlang VM | Statement: [Phoenix, uses, Erlang VM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Erlang VM Context triple: [Phoenix, uses, Erlang VM]
-
A.
Erlang VM
chosen
The Erlang VM (BEAM) is a highly concurrent, fault-tolerant virtual machine designed for building scalable, distributed systems and real-time applications.
-
B.
Erlang
Erlang is a functional, concurrent programming language designed for building highly scalable, fault-tolerant distributed systems, originally developed by Ericsson for telecom applications.
-
C.
K Virtual Machine
K Virtual Machine is a lightweight Java virtual machine designed for resource-constrained devices such as mobile phones and embedded systems.
-
D.
Elixir
Elixir is a functional, concurrent programming language built on the Erlang VM, known for its scalability, fault tolerance, and expressive syntax.
-
E.
Eiffel runtime environment
Eiffel runtime environment is the execution platform and supporting system that runs programs written in the Eiffel programming language, providing services such as memory management, exception handling, and support for Eiffel’s Design by Contract features.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a022323e2c08190b8a86b865a14dbbe |
completed | May 11, 2026, 6:42 p.m. |
Created at: April 10, 2026, 10 a.m.