Triple
T15605861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 FIBA Africa Championship |
E375157
|
entity |
| Predicate | finalScoreMargin |
P39190
|
FINISHED |
| Object | single-digit points |
—
|
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: single-digit points | Statement: [2011 FIBA Africa Championship, finalScoreMargin, single-digit points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreMargin Context triple: [2011 FIBA Africa Championship, finalScoreMargin, single-digit points]
-
A.
finalRoundMargin
chosen
Indicates the point or score difference between competitors in the final round of a contest or competition.
-
B.
scoreMargin
Indicates the difference in score between two competitors or sides in a contest or game.
-
C.
averageMarginOfVictory
Indicates the typical point or score difference by which one competitor or team wins over opponents across a set of contests or games.
-
D.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
winningTeamScore
Indicates the number of points or goals achieved by the team that wins a particular game or competition.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7d9328819090e93d55881269a5 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.