Triple
T37011807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Shadowkeep |
E915969
|
entity |
| Predicate | campaignTitle |
P82481
|
FINISHED |
| Object | Shadowkeep campaign |
—
|
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: Shadowkeep campaign | Statement: [Destiny 2: Shadowkeep, campaignTitle, Shadowkeep campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignTitle Context triple: [Destiny 2: Shadowkeep, campaignTitle, Shadowkeep campaign]
-
A.
campaignTheme
Indicates the central idea or message that characterizes and unifies a particular campaign.
-
B.
campaignDescriptor
chosen
Indicates that one entity serves as a descriptive label or characterization for a particular campaign associated with another entity.
-
C.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
D.
campaignRibbon
Indicates that an entity has been awarded or is associated with a specific campaign ribbon recognizing participation in a particular military or organizational campaign.
-
E.
promotionalCampaign
Indicates a relationship where one entity organizes or runs a coordinated set of marketing activities aimed at promoting another entity, product, or service.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.