Triple
T21718671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtuality |
E536096
|
entity |
| Predicate | usesTechnologyInStory |
P145083
|
FINISHED |
| Object | immersive virtual reality modules |
—
|
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: immersive virtual reality modules | Statement: [Virtuality, usesTechnologyInStory, immersive virtual reality modules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTechnologyInStory Context triple: [Virtuality, usesTechnologyInStory, immersive virtual reality modules]
-
A.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
B.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
C.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
-
D.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
-
E.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
- F. None of above. chosen
Provenance (4 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96cc58081908dda09819041b888 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:47 p.m.