Triple
T14055551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Demon |
E338209
|
entity |
| Predicate | virtualRealityRemoved |
P112650
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [The Demon, virtualRealityRemoved, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtualRealityRemoved Context triple: [The Demon, virtualRealityRemoved, 2023]
-
A.
hasVirtualExperience
Indicates that one entity possesses or has participated in a virtual or digitally simulated experience related to another entity.
-
B.
viewOnReality
Indicates a subject’s overarching perspective, interpretation, or conceptual stance regarding the nature of reality.
-
C.
supportsPCVRConnection
Indicates that an entity enables or is compatible with establishing a PC-based virtual reality (VR) connection.
-
D.
vanishIn
Indicates that one entity disappears or ceases to be perceptible within, or as part of, another entity or context.
-
E.
hasOculus
Indicates that one entity possesses or is equipped with an oculus (a circular opening or eye-like feature).
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8d1aa48190a5055d15d9fa220c |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.