Triple
T37179222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident Evil 7: Biohazard |
E921145
|
entity |
| Predicate | hasMultiplatformRelease |
P49320
|
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, hasMultiplatformRelease, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplatformRelease Context triple: [Resident Evil 7: Biohazard, hasMultiplatformRelease, yes]
-
A.
isMultiplatform
chosen
Indicates that something is designed to operate or be available across multiple platforms or environments.
-
B.
hasOnlinePlatformRelease
Indicates that an entity has been released or made available through an online platform or digital service.
-
C.
hasCompanionPlatform
Indicates that an entity is associated with or supported by an additional platform that accompanies or complements it.
-
D.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
E.
intendedReleasePlatform
Indicates the platform or medium for which something (such as a product, work, or content) is planned or designated to be released.
- 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_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:15 p.m.