Triple
T11389814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 NCAA Division I men's basketball tournament |
E269804
|
entity |
| Predicate | finalFourCountForMichigan |
P12670
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [1993 NCAA Division I men's basketball tournament, finalFourCountForMichigan, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalFourCountForMichigan Context triple: [1993 NCAA Division I men's basketball tournament, finalFourCountForMichigan, 5]
-
A.
numberOfFinalFourTeams
Indicates the count of teams that reached the Final Four stage in a given tournament or competition.
-
B.
finalFourCountForChampion
Indicates the number of times a champion has reached the Final Four in the relevant competition or tournament.
-
C.
finalFourAppearance
Indicates that an entity has reached the semifinal round (Final Four) of a tournament or championship.
-
D.
FinalFourAppearances
chosen
Indicates the number of times a team has reached the semifinal round (Final Four) of a tournament or championship.
-
E.
finalFourState
Indicates that a team or participant reached the semifinal round (Final Four) of a tournament held in a particular state.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.