Triple
T6003006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Hoosiers men's basketball |
E133640
|
entity |
| Predicate | undefeatedRegularSeason |
P63159
|
FINISHED |
| Object | 1975–76 |
—
|
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: 1975–76 | Statement: [Indiana Hoosiers men's basketball, undefeatedRegularSeason, 1975–76]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undefeatedRegularSeason Context triple: [Indiana Hoosiers men's basketball, undefeatedRegularSeason, 1975–76]
-
A.
unbeatenLeagueSeason
Indicates that a team completed an entire league season without losing any match.
-
B.
isUndefeated
chosen
Indicates that an entity has not been defeated in any relevant contest, match, or competition.
-
C.
unbeatenStreakYears
Indicates the number of consecutive years during which an entity has remained unbeaten or undefeated.
-
D.
championRegularSeasonRecord
Indicates that an entity is the champion associated with a particular regular season record.
-
E.
regularSeasonWins
Indicates the number of games a team wins during the regular season of a 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.