Triple
T17674826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAM virtual machine |
E440619
|
entity |
| Predicate | supportsLanguage |
P2177
|
FINISHED |
| Object | LFE |
—
|
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: LFE | Statement: [BEAM virtual machine, supportsLanguage, LFE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFE Context triple: [BEAM virtual machine, supportsLanguage, LFE]
-
A.
LFE
chosen
LFE (Lisp Flavoured Erlang) is a Lisp dialect that runs on the Erlang virtual machine, combining Lisp syntax with Erlang’s concurrency and fault-tolerance features.
-
B.
Elixir
Elixir is a functional, concurrent programming language built on the Erlang VM, known for its scalability, fault tolerance, and expressive syntax.
-
C.
LFLX
LFLX is the ICAO airport code for Châteauroux-Centre "Marcel Dassault" Airport in central France, a facility known for cargo operations, aircraft maintenance, and pilot training.
-
D.
LFO
LFO is a pioneering British electronic music act known for helping define the early 1990s techno and bleep scene.
-
E.
FLE
FLE is the National Rail station code for Fleet railway station in Hampshire, England.
- 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_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.