Triple
T10608660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | original 13 rules of basketball |
E275943
|
entity |
| Predicate | shotClockMentioned |
P50673
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [original 13 rules of basketball, shotClockMentioned, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shotClockMentioned Context triple: [original 13 rules of basketball, shotClockMentioned, no]
-
A.
shotClock
chosen
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.
threePointContestHeld
Indicates that a three-point shooting contest event has taken place or been conducted.
-
D.
MVPShotsOnGoal
Indicates that the entity identified as the MVP recorded a certain number of shots on goal in a game or competition.
-
E.
usedInPlayByPlayFor
Indicates that something (such as data, terminology, or a resource) is utilized within the context of a play-by-play account or commentary.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4d0a6881909fea20378085173d |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.