Triple
T2988680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 NCAA Division I men's basketball championship |
E80690
|
entity |
| Predicate | titleCountForChampion |
P4419
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2003 NCAA Division I men's basketball championship, titleCountForChampion, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCountForChampion Context triple: [2003 NCAA Division I men's basketball championship, titleCountForChampion, 1]
-
A.
leagueChampionFranchisePennantCount
Indicates the number of league championship pennants won by a given franchise.
-
B.
leagueOfChampion
Indicates that an entity is the league or competition in which a given champion or titleholder competes or holds their status.
-
C.
titleCount
chosen
Indicates the number of distinct titles associated with an entity within a given context.
-
D.
firstChampion
Indicates that one entity is the earliest or original champion or title-holder in relation to another entity.
-
E.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c9cdd081908fa8094a3ac1f8d3 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.