Triple
T11290133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Black Ops II |
E267302
|
entity |
| Predicate | multiplayerMapCountAtLaunch |
P98328
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Call of Duty: Black Ops II, multiplayerMapCountAtLaunch, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiplayerMapCountAtLaunch Context triple: [Call of Duty: Black Ops II, multiplayerMapCountAtLaunch, 14]
-
A.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
B.
dungeonCountAtLaunch
Indicates the number of dungeons available when the game or content is first released.
-
C.
multiplayerFeature
Indicates that the subject supports or involves multiple users participating together, typically at the same time within the same activity or environment.
-
D.
laterEditionApproximateNumberOfMaps
Indicates that a later edition of a work contains approximately the specified number of maps.
-
E.
numberOfPlayersLAN
Indicates the number of players that can participate together over a local area network (LAN) in the related context.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98875a08190b8509fe55e49d52d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.