Triple
T37503471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descent |
E932030
|
entity |
| Predicate | hasSettingInZombiesMap |
P98329
|
FINISHED |
| Object | Stalingrad |
—
|
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: Stalingrad | Statement: [Descent, hasSettingInZombiesMap, Stalingrad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingInZombiesMap Context triple: [Descent, hasSettingInZombiesMap, Stalingrad]
-
A.
hasZombiesMap
chosen
Indicates that an entity is associated with or contains a map or layout specifically involving zombies.
-
B.
hasAttackingTeamSpawn
Indicates that a location or point is designated as the spawn area for the attacking team.
-
C.
hasMobSpawnRate
Indicates the rate or frequency at which mobs are generated or spawned in a given context.
-
D.
hasStalkerElement
Indicates that one entity persistently and obsessively follows, monitors, or harasses another entity in an unwanted or intrusive manner.
-
E.
hasDemilitarizedOrSpecialZones
Indicates that there exist designated areas between or within territories where military presence or activities are restricted or specially regulated.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
Created at: May 3, 2026, 4:17 p.m.