Triple
T38476745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vengeance DLC pack |
E915568
|
entity |
| Predicate | dlcNumberInSeason |
P188406
|
FINISHED |
| Object | third DLC pack for Call of Duty: Black Ops II |
—
|
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: third DLC pack for Call of Duty: Black Ops II | Statement: [Vengeance DLC pack, dlcNumberInSeason, third DLC pack for Call of Duty: Black Ops II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dlcNumberInSeason Context triple: [Vengeance DLC pack, dlcNumberInSeason, third DLC pack for Call of Duty: Black Ops II]
-
A.
DLCNumber
chosen
Indicates the identifier or count assigned to a specific downloadable content (DLC) item associated with something.
-
B.
hasDLC
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
C.
DLCName
Indicates that the associated value is the name or title of a specific downloadable content (DLC) package related to the entity.
-
D.
franchiseSeasonNumber
Indicates the specific season number assigned to an installment within a larger franchise series.
-
E.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.