Triple
T37179209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident Evil 7: Biohazard |
E921145
|
entity |
| Predicate | franchiseRevival |
P28354
|
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, franchiseRevival, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseRevival Context triple: [Resident Evil 7: Biohazard, franchiseRevival, yes]
-
A.
franchiseReactivated
chosen
Indicates that a previously inactive or terminated franchise has been restored to active operational status.
-
B.
franchiseLegacy
Indicates that an entity continues, inherits, or extends the storyline, brand, or creative universe established by an earlier work in the same franchise.
-
C.
franchiseContinuedAs
Indicates that an existing franchise was succeeded or carried on by another franchise, continuing its storyline, brand, or concept.
-
D.
emergentFranchise
Indicates that a franchise is in the process of forming or newly developing, rather than being fully established or mature.
-
E.
franchiseRenamedAs
Indicates that an existing franchise has changed its official name to a new one.
- 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:15 p.m.