Triple
T25817218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackbox Party Pack 7 |
E650288
|
entity |
| Predicate | supportsAudienceParticipation |
P45833
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jackbox Party Pack 7, supportsAudienceParticipation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAudienceParticipation Context triple: [Jackbox Party Pack 7, supportsAudienceParticipation, true]
-
A.
hasAudienceParticipation
chosen
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
B.
supportsAudienceSize
Indicates that one entity is capable of accommodating or handling an audience of a specified size.
-
C.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
D.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
-
E.
allowsParticipationIn
Indicates that one entity grants another entity the right or permission to take part in a specific activity, event, or process.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 22, 2026, 7:27 a.m.