Triple
T16000029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident Evil Code: Veronica X |
E388068
|
entity |
| Predicate | addsContent |
P4097
|
FINISHED |
| Object | additional cutscenes |
—
|
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: additional cutscenes | Statement: [Resident Evil Code: Veronica X, addsContent, additional cutscenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsContent Context triple: [Resident Evil Code: Veronica X, addsContent, additional cutscenes]
-
A.
addsContentType
Indicates that one entity augments or associates another entity with a specific content type.
-
B.
publishesContent
Indicates that one entity makes content created by another entity publicly available or distributed through some medium.
-
C.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
D.
collectsContent
Indicates that one entity gathers, acquires, or accumulates content from another entity or source.
-
E.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.