Triple
T9032998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Summer Olympics men's basketball |
E216418
|
entity |
| Predicate | finalScoreGoldMedalGame |
P72761
|
FINISHED |
| Object | 85–75 |
—
|
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: 85–75 | Statement: [2000 Summer Olympics men's basketball, finalScoreGoldMedalGame, 85–75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreGoldMedalGame Context triple: [2000 Summer Olympics men's basketball, finalScoreGoldMedalGame, 85–75]
-
A.
olympicGoldMedalFinalScore
chosen
Indicates the final score or result by which an athlete or team secured an Olympic gold medal in a given event.
-
B.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
game6FinalScore
Indicates the final score achieved in the sixth game of a series or sequence of games.
-
D.
goldMedalGameFor
Indicates that the referenced game is the one in which the gold medal is contested or awarded for a particular event or competition.
-
E.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa0c89c81909792190f08fef8df |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.