Triple
T31022693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 Olympic tournament |
E790490
|
entity |
| Predicate | restartRule |
P170919
|
FINISHED |
| Object | check-ball at top of 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: check-ball at top of arc | Statement: [FIBA 3x3 Olympic tournament, restartRule, check-ball at top of arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartRule Context triple: [FIBA 3x3 Olympic tournament, restartRule, check-ball at top of arc]
-
A.
resetRule
Indicates that a rule is returned to its initial or default state, typically clearing any prior changes or accumulated effects.
-
B.
restartPolicy
Indicates the rules governing if and how an action, process, or task should automatically restart after it stops or fails.
-
C.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
-
D.
relatedRestart
Indicates that one process, event, or state is connected to or causes the restarting of another process, event, or state.
-
E.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:58 p.m.