Triple
T11308823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 NCAA Division I men's basketball tournament |
E267784
|
entity |
| Predicate | finalFourCountForChampion |
P98424
|
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: [1992 NCAA Division I men's basketball tournament, finalFourCountForChampion, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalFourCountForChampion Context triple: [1992 NCAA Division I men's basketball tournament, finalFourCountForChampion, 5]
-
A.
runnerUpFinalFourCount
Indicates the number of times an entity has finished as the runner-up in a Final Four stage of a competition or tournament.
-
B.
finalFourAppearance
Indicates that an entity has reached the semifinal round (Final Four) of a tournament or championship.
-
C.
numberOfGamesInFinals
Indicates the total count of games played in the finals stage of a competition or series.
-
D.
finalsChampion
Indicates that an entity is the winner or champion of a particular final match, series, or tournament.
-
E.
finalFourAppearancesWith
Indicates that the entities have appeared together in the NCAA basketball Final Four in the same tournament.
- F. None of above. chosen
Provenance (4 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9bf87d88190904c2d174578ebbf |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.