Triple
T10608664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | original 13 rules of basketball |
E275943
|
entity |
| Predicate | originalRestartMethod |
P72048
|
FINISHED |
| Object | jump ball after each goal |
—
|
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: jump ball after each goal | Statement: [original 13 rules of basketball, originalRestartMethod, jump ball after each goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRestartMethod Context triple: [original 13 rules of basketball, originalRestartMethod, jump ball after each goal]
-
A.
relatedRestart
chosen
Indicates that one process, event, or state is connected to or causes the restarting of another process, event, or state.
-
B.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
-
C.
reconstructionStart
Indicates the point in time or event at which a reconstruction process or activity begins.
-
D.
alternativeLaunchMethod
Indicates that there exists a different or non-standard method by which the launch of something can be carried out.
-
E.
restartCapability
Indicates the ability or permission for an entity to be restarted, typically after a stop, failure, or configuration change.
- 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.