Triple
T12160204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Modern Warfare II (2022) |
E289682
|
entity |
| Predicate | hasThirdPersonPlaylist |
P103267
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Call of Duty: Modern Warfare II (2022), hasThirdPersonPlaylist, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThirdPersonPlaylist Context triple: [Call of Duty: Modern Warfare II (2022), hasThirdPersonPlaylist, yes]
-
A.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
B.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
C.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
D.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
E.
supportsPlaylists
Indicates that one entity provides functionality for creating, managing, or using playlists associated with another entity.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d915d58ab881908b5b7901990308a4 |
completed | April 10, 2026, 3:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.