Triple
T32629185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Forgotten Room |
E834154
|
entity |
| Predicate | narrativeRelationToGame |
P51756
|
FINISHED |
| Object | side story |
—
|
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: side story | Statement: [The Forgotten Room, narrativeRelationToGame, side story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRelationToGame Context triple: [The Forgotten Room, narrativeRelationToGame, side story]
-
A.
mentionedInGame
Indicates that an entity is referenced or cited within the content or dialogue of a game.
-
B.
narrativeConnection
chosen
Indicates a meaningful relationship between elements within a narrative, such as events, characters, or scenes, that links them in terms of plot, causality, or thematic continuity.
-
C.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
D.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
E.
inNarrativeRole
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:07 a.m.