Triple
T36853181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Finest Hour |
E910723
|
entity |
| Predicate | featuresCampaign |
P205082
|
FINISHED |
| Object | Soviet campaign |
—
|
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: Soviet campaign | Statement: [Call of Duty: Finest Hour, featuresCampaign, Soviet campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCampaign Context triple: [Call of Duty: Finest Hour, featuresCampaign, Soviet campaign]
-
A.
featuresPromotion
Indicates that something includes, offers, or presents a promotion as part of its content or configuration.
-
B.
campaignDescriptor
Indicates that one entity serves as a descriptive label or characterization for a particular campaign associated with another entity.
-
C.
campaignOrService
Indicates that one entity is a campaign and the other is a service that the campaign promotes, uses, or is associated with.
-
D.
featuresPublisher
Indicates that one entity highlights, showcases, or gives prominent placement to a publisher.
-
E.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.