Triple
T37503391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revelations |
E932027
|
entity |
| Predicate | dlcPackOf |
P39175
|
FINISHED |
| Object | Call of Duty: Black Ops III Salvation DLC |
—
|
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: Black Ops III Salvation DLC | Statement: [Revelations, dlcPackOf, Call of Duty: Black Ops III Salvation DLC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dlcPackOf Context triple: [Revelations, dlcPackOf, Call of Duty: Black Ops III Salvation DLC]
-
A.
hasDLC
chosen
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
B.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
C.
DLCName
Indicates that the associated value is the name or title of a specific downloadable content (DLC) package related to the entity.
-
D.
distributionPackage
Indicates that one entity is a package or bundle used to distribute another entity (such as software, content, or resources).
-
E.
bundle
Indicates that multiple items are grouped or packaged together as a single combined unit or offering.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.