Triple

T25734108
Position Surface form Disambiguated ID Type / Status
Subject Jackbox Party Pack 4 E645326 entity
Predicate requiresInternetForControllers P33694 FINISHED
Object yes 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: yes | Statement: [Jackbox Party Pack 4, requiresInternetForControllers, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresInternetForControllers
Context triple: [Jackbox Party Pack 4, requiresInternetForControllers, yes]
  • A. networkRequirement chosen
    Indicates that one entity requires access to or use of another entity’s network resources or connectivity to function or be fulfilled.
  • B. requiresApplicationTo
    Indicates that one entity can only access, use, or obtain another entity if a formal application or request process is completed.
  • C. requiresConfiguration
    Indicates that one entity depends on another to be set up or configured before it can function or be used.
  • D. requiresSoftware
    Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
  • E. requiresContext
    Indicates that the relationship or action cannot be properly understood or evaluated without additional surrounding information, conditions, or circumstances.
  • 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_69f6978fe97081908fe568091ad9b159 completed May 3, 2026, 12:32 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
Created at: April 21, 2026, 11:21 p.m.