Triple
T22288082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 rules |
E550915
|
entity |
| Predicate | shotClockDevice |
P5737
|
FINISHED |
| Object | visible 12-second shot clock is required |
—
|
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: visible 12-second shot clock is required | Statement: [FIBA 3x3 rules, shotClockDevice, visible 12-second shot clock is required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shotClockDevice Context triple: [FIBA 3x3 rules, shotClockDevice, visible 12-second shot clock is required]
-
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
Indicates the length of time allotted on the shot clock for a team to attempt a shot before a violation occurs.
-
C.
shotType
Indicates the specific kind or category of shot used or taken in a given context (e.g., in film, photography, or sports).
-
D.
screenTime
Indicates the amount of time an entity spends viewing or interacting with a screen-based device.
-
E.
hasClock
chosen
Indicates that one entity possesses, contains, or is equipped with a clock.
- 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.