Triple
T36965214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Silent |
E914409
|
entity |
| Predicate | developedEntryInSeries |
P56660
|
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: [Team Silent, developedEntryInSeries, Silent Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedEntryInSeries Context triple: [Team Silent, developedEntryInSeries, Silent Hill]
-
A.
directedEntryInSeries
Indicates that an entity directed a specific installment or entry within a larger series.
-
B.
developedSeries
chosen
Indicates that one entity is responsible for creating or developing a particular series associated with the other entity.
-
C.
seriesEntryOf
Indicates that one item functions as an individual entry, installment, or component within a larger series.
-
D.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
E.
belongsToSeriesEntry
Indicates that something is an individual installment or component within a larger series or 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:14 p.m.