Triple
T17674806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erlang VM |
E440618
|
entity |
| Predicate | compilationTarget |
P29008
|
FINISHED |
| Object | BEAM bytecode |
—
|
LITERAL 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: BEAM bytecode | Statement: [Erlang VM, compilationTarget, BEAM bytecode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilationTarget Context triple: [Erlang VM, compilationTarget, BEAM bytecode]
-
A.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
B.
compiledTo
chosen
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
C.
compilationSpeed
Indicates how quickly a program or source code is processed and transformed into executable form by a compiler.
-
D.
backendTarget
Indicates that one entity serves as the backend system, service, or endpoint that another entity connects to or depends on for processing or functionality.
-
E.
compilation
Indicates the process or result of collecting and assembling various items, works, or elements into a single organized whole.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.