Triple
T36937106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Vanguard (support studio) |
E913648
|
entity |
| Predicate | gameSettingWorkedOn |
P186709
|
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: [Call of Duty: Vanguard (support studio), gameSettingWorkedOn, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameSettingWorkedOn Context triple: [Call of Duty: Vanguard (support studio), gameSettingWorkedOn, World War II]
-
A.
gameEngineWork
Indicates that an entity works on, contributes to, or is employed in the development or maintenance of a game engine.
-
B.
worksInSetting
Indicates that an entity performs its activities or functions within a specified environment, context, or setting.
-
C.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
D.
gameModeDesign
Indicates that one entity defines or specifies the rules, structure, or configuration of a particular game mode for another entity.
-
E.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
- F. None of above. chosen
Provenance (4 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.