Triple
T37179223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident Evil 7: Biohazard |
E921145
|
entity |
| Predicate | hasVRSupport |
P167454
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Resident Evil 7: Biohazard, hasVRSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVRSupport Context triple: [Resident Evil 7: Biohazard, hasVRSupport, yes]
-
A.
supportsPCVRConnection
Indicates that an entity enables or is compatible with establishing a PC-based virtual reality (VR) connection.
-
B.
hasOculus
Indicates that one entity possesses or is equipped with an oculus (a circular opening or eye-like feature).
-
C.
virtualRealityOption
chosen
Indicates that an entity offers, supports, or is configured as a virtual reality mode, feature, or setting within a system or experience.
-
D.
supportsOculusLink
Indicates that one entity is compatible with and can operate using the Oculus Link connection feature provided by another entity.
-
E.
virtualRealityProvider
Indicates that one entity serves as a provider or supplier of virtual reality services, systems, or experiences to 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.