Triple
T37538723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Call of Duty League season |
E933272
|
entity |
| Predicate | previousTeamSizeRule |
P107928
|
FINISHED |
| Object | 5 starting players per team in 2020 season |
—
|
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: 5 starting players per team in 2020 season | Statement: [2021 Call of Duty League season, previousTeamSizeRule, 5 starting players per team in 2020 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousTeamSizeRule Context triple: [2021 Call of Duty League season, previousTeamSizeRule, 5 starting players per team in 2020 season]
-
A.
rosterSize
Indicates the total number of individuals included on a given roster.
-
B.
competitionSquadRule
chosen
Indicates the rules or constraints governing how squads or teams must be composed or registered for a particular competition.
-
C.
leagueSizeContext
Indicates the contextual information or conditions under which the size of a league is defined, measured, or interpreted.
-
D.
squadSizeType
Indicates the type or classification of a squad based on its size.
-
E.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:17 p.m.