Triple
T26050487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2024 NCAA Division I men's basketball tournament |
E647958
|
entity |
| Predicate | championshipGameLoserPoints |
P48567
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [2024 NCAA Division I men's basketball tournament, championshipGameLoserPoints, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipGameLoserPoints Context triple: [2024 NCAA Division I men's basketball tournament, championshipGameLoserPoints, 60]
-
A.
game7LoserPoints
Indicates the number of points scored by the team that lost in game 7 of a series or matchup.
-
B.
pointsScoredByLosingTeam
chosen
Indicates the number of points scored by the team that did not win in a given game or match.
-
C.
championshipGameScore
Indicates the final score achieved by each participant in a championship game.
-
D.
loserPoints
Indicates the number of points awarded to or accumulated by the losing side in a competitive event or comparison.
-
E.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065e26748190bac3160a91599913 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 9:10 a.m.