Triple
T11290131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Black Ops II |
E267302
|
entity |
| Predicate | campaignStructure |
P672
|
FINISHED |
| Object | branching narrative |
—
|
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: branching narrative | Statement: [Call of Duty: Black Ops II, campaignStructure, branching narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignStructure Context triple: [Call of Duty: Black Ops II, campaignStructure, branching narrative]
-
A.
campaignManager
Indicates that one entity serves as the manager or coordinator responsible for planning, executing, and overseeing a campaign on behalf of another entity.
-
B.
campaignType
chosen
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
C.
campaignSetting
Indicates the broader narrative world or environment within which a particular campaign, story, or activity takes place.
-
D.
plannedCampaign
Indicates that an entity has designed and scheduled a campaign to be executed in the future.
-
E.
campaignDescriptor
Indicates that one entity serves as a descriptive label or characterization for a particular campaign 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98875a08190b8509fe55e49d52d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.