Triple
T3501292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Fighting Illini men's basketball |
E73973
|
entity |
| Predicate | hasWonConferenceTournamentTitles |
P13754
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Illinois Fighting Illini men's basketball, hasWonConferenceTournamentTitles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonConferenceTournamentTitles Context triple: [Illinois Fighting Illini men's basketball, hasWonConferenceTournamentTitles, true]
-
A.
conferenceTournamentTitles
chosen
Indicates the number of conference tournament championships an entity has won.
-
B.
hasWonNCAATitleIn
Indicates that an entity has won an NCAA championship title in a specified sport, category, or year.
-
C.
wonConferenceTitle
Indicates that an entity secured the championship or first-place title in a conference-level competition or league.
-
D.
team1ConferenceTitles
Indicates the number of conference championship titles won by the first team in a given context or comparison.
-
E.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd5fbe8819091b61fa8df355f0c |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.