Triple
T37705020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Modern Warfare 2 Campaign Remastered |
E939175
|
entity |
| Predicate | campaignFrom |
P188954
|
FINISHED |
| Object | Call of Duty: Modern Warfare 2 |
—
|
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: Call of Duty: Modern Warfare 2 | Statement: [Call of Duty: Modern Warfare 2 Campaign Remastered, campaignFrom, Call of Duty: Modern Warfare 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignFrom Context triple: [Call of Duty: Modern Warfare 2 Campaign Remastered, campaignFrom, Call of Duty: Modern Warfare 2]
-
A.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
B.
campaignOrService
Indicates that one entity is a campaign and the other is a service that the campaign promotes, uses, or is associated with.
-
C.
campaignFormat
Indicates the specific structural or stylistic format in which a campaign is designed or delivered (e.g., type, layout, or presentation style).
-
D.
launchCampaign
Indicates initiating and putting into operation a planned promotional or marketing campaign.
-
E.
campaignMethod
Indicates the method or approach used to conduct or deliver a campaign.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.