Triple
T22288075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 rules |
E550915
|
entity |
| Predicate | shotClockResetAfterDefensiveRebound |
P19202
|
FINISHED |
| Object | 12 seconds |
—
|
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: 12 seconds | Statement: [FIBA 3x3 rules, shotClockResetAfterDefensiveRebound, 12 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shotClockResetAfterDefensiveRebound Context triple: [FIBA 3x3 rules, shotClockResetAfterDefensiveRebound, 12 seconds]
-
A.
shotClock
Indicates that a time limit is imposed on an offensive possession or action, after which a violation occurs if a shot or required attempt has not been made.
-
B.
shotClockDuration
chosen
Indicates the length of time allotted on the shot clock for a team to attempt a shot before a violation occurs.
-
C.
backcourtViolationTime
Indicates the amount of time elapsed leading to or associated with a backcourt violation in a basketball game.
-
D.
introducedDefensiveThreeSeconds
Indicates that an entity (such as a league or rules committee) instituted the defensive three-second rule, establishing a restriction on how long defenders may remain in the key.
-
E.
freeThrowPoints
Indicates the number of points a player scores specifically from successful free throw attempts.
- 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_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. |
Created at: April 16, 2026, 8:40 p.m.