Triple
T38642872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stimulus Package |
E938645
|
entity |
| Predicate | includesRemadeMapFrom |
P191164
|
FINISHED |
| Object | Call of Duty 4: Modern Warfare |
E273665
|
NE 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: Call of Duty 4: Modern Warfare | Statement: [Stimulus Package, includesRemadeMapFrom, Call of Duty 4: Modern Warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRemadeMapFrom Context triple: [Stimulus Package, includesRemadeMapFrom, Call of Duty 4: Modern Warfare]
-
A.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
-
B.
hasRemakeBy
Indicates that an original work has been remade or re-created by a specified agent (such as a person, studio, or organization).
-
C.
remadeFor
Indicates that one work has been recreated or adapted specifically for another context, audience, or medium.
-
D.
reimaginesMap
chosen
Indicates that one entity conceptually redesigns or reconceptualizes the structure, layout, or organization represented by another entity’s map.
-
E.
containsReimaginedVersionsOf
Indicates that one entity includes or incorporates updated, reinterpreted, or newly imagined versions of another entity.
- F. None of above.
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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a465ea4b0b081908bbc72cde3eed0ec |
completed | July 2, 2026, 12:50 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.