Triple
T37599679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Call of Duty League season |
E935488
|
entity |
| Predicate | basedOnTitle |
P99044
|
FINISHED |
| Object | Call of Duty: Vanguard competitive multiplayer |
—
|
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: Vanguard competitive multiplayer | Statement: [2022 Call of Duty League season, basedOnTitle, Call of Duty: Vanguard competitive multiplayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnTitle Context triple: [2022 Call of Duty League season, basedOnTitle, Call of Duty: Vanguard competitive multiplayer]
-
A.
titleBasedIn
Indicates that a creative work’s title is derived from, inspired by, or directly taken from a particular source or context.
-
B.
titleBasis
chosen
Indicates that one entity serves as the basis or source material for the title or name of another entity.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
basedOnText
Indicates that something is derived, adapted, or developed from a specific text source.
-
E.
basedOnName
Indicates that one entity is derived, determined, or identified using the name of another 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 3, 2026, 4:18 p.m.