Triple
T25878710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackbox Party Pack 8 |
E651981
|
entity |
| Predicate | supportsPlayersPerGame |
P191665
|
FINISHED |
| Object | 1-10 (varies by game) |
—
|
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: 1-10 (varies by game) | Statement: [Jackbox Party Pack 8, supportsPlayersPerGame, 1-10 (varies by game)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayersPerGame Context triple: [Jackbox Party Pack 8, supportsPlayersPerGame, 1-10 (varies by game)]
-
A.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
B.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
C.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
D.
teamCountPerGame
Indicates the number of teams that participate in a single game or match.
-
E.
allowsOveragePlayers
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
- F. None of above. chosen
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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 22, 2026, 8:13 a.m.