Triple
T34969183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Killing Game |
E1008486
|
entity |
| Predicate | holodeckSetting |
P1957
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [The Killing Game, holodeckSetting, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holodeckSetting Context triple: [The Killing Game, holodeckSetting, World War II]
-
A.
apparitionSetting
Indicates the context or environment in which an apparition or ghostly manifestation appears.
-
B.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
C.
eraOfSetting
Indicates the historical or temporal period in which the setting of something (such as a story, event, or work) takes place.
-
D.
setting
chosen
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
E.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.