Triple

T22288061
Position Surface form Disambiguated ID Type / Status
Subject FIBA 3x3 rules E550915 entity
Predicate timeoutAllocation P147912 FINISHED
Object 1 team timeout per 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 team timeout per game | Statement: [FIBA 3x3 rules, timeoutAllocation, 1 team timeout per game]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeoutAllocation
Context triple: [FIBA 3x3 rules, timeoutAllocation, 1 team timeout per game]
  • A. timeoutRule
    Indicates a rule that defines when and under what conditions an operation, request, or process should automatically time out.
  • B. timeLimited
    Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
  • C. strategicTimeoutFor
    Indicates that one entity initiates or designates a strategic timeout specifically for another entity (such as a team, player, or process).
  • D. defaultLoginTimeout
    Indicates the standard amount of time a login session or login attempt is allowed to remain active before it automatically expires or times out.
  • E. agingTimeMaximum
    Indicates the maximum duration for which something is allowed or expected to age before it is considered expired, mature, or no longer valid.
  • 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_69e11e44d538819097c6b8f333af3352 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1560896348190985725ac8ad406b3 completed April 29, 2026, 12:51 a.m.
PD Predicate disambiguation batch_69e72ffa438481908f80879aef2a589b completed April 21, 2026, 8:06 a.m.
PDg Predicate description generation batch_69e75dc7b08081909d64441e979c2fa4 completed April 21, 2026, 11:21 a.m.
Created at: April 16, 2026, 8:40 p.m.