Triple
T38476742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vengeance DLC pack |
E915568
|
entity |
| Predicate | settingOfZombiesMap |
P98329
|
FINISHED |
| Object | Western-style underground town |
—
|
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: Western-style underground town | Statement: [Vengeance DLC pack, settingOfZombiesMap, Western-style underground town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfZombiesMap Context triple: [Vengeance DLC pack, settingOfZombiesMap, Western-style underground town]
-
A.
hasZombiesMap
chosen
Indicates that an entity is associated with or contains a map or layout specifically involving zombies.
-
B.
mapSetting
Indicates a configuration relationship where a map is assigned specific settings or parameters that determine how it is displayed or behaves.
-
C.
multiplayerMap
Indicates that a map or environment is designed to support gameplay involving multiple players simultaneously.
-
D.
settingOfDeath
Indicates the specific place or environment in which an entity’s death occurred.
-
E.
mapGeneration
Indicates the process or action of creating or producing a map from given data or parameters.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:31 p.m.