Triple
T37096762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silent Hill 3 |
E918582
|
entity |
| Predicate | directNarrativeSequelTo |
P1961
|
FINISHED |
| Object | Silent Hill |
—
|
NE NERFINISHED |
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: Silent Hill | Statement: [Silent Hill 3, directNarrativeSequelTo, Silent Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directNarrativeSequelTo Context triple: [Silent Hill 3, directNarrativeSequelTo, Silent Hill]
-
A.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
-
B.
sequelDirected
Indicates that one work is a sequel to another and was directed by the same director or a specific director associated with that sequel relationship.
-
C.
hasSequelDepiction
Indicates that one depiction of something is followed by another depiction that continues its story or sequence.
-
D.
hasSequel
chosen
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
E.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.