Triple
T38581971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control (Call of Duty game mode) |
E932265
|
entity |
| Predicate | mapDesignFocus |
P123882
|
FINISHED |
| Object | multiple objective zones |
—
|
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: multiple objective zones | Statement: [Control (Call of Duty game mode), mapDesignFocus, multiple objective zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapDesignFocus Context triple: [Control (Call of Duty game mode), mapDesignFocus, multiple objective zones]
-
A.
mapsFocus
chosen
Indicates that one entity serves as the primary subject, area, or aspect of attention, emphasis, or concentration for another entity.
-
B.
mapDesigner
Indicates that an entity is the designer or creator responsible for producing a particular map.
-
C.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
D.
mapSetting
Indicates a configuration relationship where a map is assigned specific settings or parameters that determine how it is displayed or behaves.
-
E.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.