Triple
T22288069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 rules |
E550915
|
entity |
| Predicate | shootingFoulOutsideArc |
P147916
|
FINISHED |
| Object | 2 free throws if shot missed outside arc |
—
|
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: 2 free throws if shot missed outside arc | Statement: [FIBA 3x3 rules, shootingFoulOutsideArc, 2 free throws if shot missed outside arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shootingFoulOutsideArc Context triple: [FIBA 3x3 rules, shootingFoulOutsideArc, 2 free throws if shot missed outside arc]
-
A.
freeThrowPoints
Indicates the number of points a player scores specifically from successful free throw attempts.
-
B.
freeThrowShooting
Indicates the action of attempting or performing a free throw in basketball.
-
C.
freeThrowStrugglesTeam
Indicates that a team has difficulty or performs poorly in making free throws.
-
D.
penaltyFrom7thFoul
Indicates that a penalty situation arises as a result of committing a seventh foul.
-
E.
freeThrowStrugglesDescription
Indicates difficulties or challenges an entity experiences when attempting or performing free throws.
- 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.