Triple
T38582150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Call of Duty League season |
E932269
|
entity |
| Predicate | introducedFranchising |
P27544
|
FINISHED |
| Object | Call of Duty esports |
—
|
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 esports | Statement: [2020 Call of Duty League season, introducedFranchising, Call of Duty esports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFranchising Context triple: [2020 Call of Duty League season, introducedFranchising, Call of Duty esports]
-
A.
franchiseStart
chosen
Indicates the point in time or event at which a franchise or franchising relationship is initiated or begins.
-
B.
establishedAsFranchise
Indicates that an entity has been set up or designated to operate as a franchise under a broader brand or business system.
-
C.
isFranchised
Indicates that an entity operates under a franchise agreement authorized by another organization or brand.
-
D.
hadFranchiseSystem
Indicates that an entity operated under or possessed a particular franchise business system or model.
-
E.
enfranchises
Indicates granting someone the legal right or privilege to participate fully in a system, typically by giving them the right to vote.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 3, 2026, 4:32 p.m.