Triple
T38476775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocalypse DLC pack |
E915569
|
entity |
| Predicate | contentFor |
P118830
|
FINISHED |
| Object | Call of Duty: Black Ops II Season Pass |
—
|
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 II Season Pass | Statement: [Apocalypse DLC pack, contentFor, Call of Duty: Black Ops II Season Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentFor Context triple: [Apocalypse DLC pack, contentFor, Call of Duty: Black Ops II Season Pass]
-
A.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
B.
collectsContent
chosen
Indicates that one entity gathers, acquires, or accumulates content from another entity or source.
-
C.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
D.
contendsFor
Indicates that an entity actively competes or strives to obtain, achieve, or win something that is also sought by others.
-
E.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
- 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_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:31 p.m.