Triple
T23033838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 World Tour |
E573540
|
entity |
| Predicate | gameEndingRule |
P25945
|
FINISHED |
| Object | first to 21 points or leading team after 10 minutes |
—
|
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: first to 21 points or leading team after 10 minutes | Statement: [FIBA 3x3 World Tour, gameEndingRule, first to 21 points or leading team after 10 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEndingRule Context triple: [FIBA 3x3 World Tour, gameEndingRule, first to 21 points or leading team after 10 minutes]
-
A.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
deathGameRule
Indicates a rule or condition within a deadly or lethal game that governs how participants must act or what consequences they face.
-
C.
gameLengthRule
chosen
Indicates a rule that specifies how long a game is allowed or required to last.
-
D.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
E.
gameWinner
Indicates which participant or team has won a particular game or match.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18482e78c8190a89681eec2edb812 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.