Triple
T38477159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classified |
E915577
|
entity |
| Predicate | mechanicsUpdate |
P189108
|
FINISHED |
| Object | Black Ops 4 perk system |
—
|
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: Black Ops 4 perk system | Statement: [Classified, mechanicsUpdate, Black Ops 4 perk system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicsUpdate Context triple: [Classified, mechanicsUpdate, Black Ops 4 perk system]
-
A.
changesMechanic
chosen
Indicates that one entity alters, replaces, or modifies the underlying rules, systems, or mechanics governing another entity or process.
-
B.
upgradeMechanism
Indicates a relationship where one entity serves as the method, process, or system by which another entity is improved, updated, or enhanced.
-
C.
mechanics
Indicates that an entity is involved in the study, design, or application of forces and motion (i.e., mechanical principles) in relation to another entity or system.
-
D.
revisionMechanism
Indicates the method or process by which something is updated, corrected, or modified over time.
-
E.
mechanicTheme
Indicates a relationship where an entity serves as the theme or primary object affected in a mechanical action or process.
- 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_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.