Triple
T25372412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dis virtual machine |
E632963
|
entity |
| Predicate | languageRuntimeFor |
P30252
|
FINISHED |
| Object | Limbo |
—
|
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: Limbo | Statement: [Dis virtual machine, languageRuntimeFor, Limbo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageRuntimeFor Context triple: [Dis virtual machine, languageRuntimeFor, Limbo]
-
A.
usesLanguageRuntime
chosen
Indicates that an entity operates using, depends on, or is executed within a specific language runtime environment.
-
B.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
C.
languageName
Indicates the specific name assigned to a language in the relationship.
-
D.
languageOfInterpretation
Indicates the language in which something (such as text, speech, or content) is interpreted or understood.
-
E.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 21, 2026, 1:38 p.m.