Triple
T25734102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackbox Party Pack 4 |
E645326
|
entity |
| Predicate | maxPlayersBracketeering |
P125759
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Jackbox Party Pack 4, maxPlayersBracketeering, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxPlayersBracketeering Context triple: [Jackbox Party Pack 4, maxPlayersBracketeering, 16]
-
A.
maximumPlayerCount
chosen
Indicates the largest number of players that can participate at the same time in the related context or activity.
-
B.
numberOfRegionalBracketsInTournament
Indicates the total count of distinct regional brackets that are included within a given tournament.
-
C.
teamMatchPlayBracketSize
Indicates the number of teams included in the bracket for a team-based match play competition.
-
D.
tournamentBracket
Indicates the structured competitive relationship among participants in a tournament, showing who faces whom and how winners advance through successive rounds.
-
E.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 11:21 p.m.