Triple
T30757192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 NCAA Division I men's basketball tournament |
E783119
|
entity |
| Predicate | eastRegionalChampion |
P116680
|
FINISHED |
| Object | UConn Huskies |
—
|
NE NERFINISHED |
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: UConn Huskies | Statement: [2014 NCAA Division I men's basketball tournament, eastRegionalChampion, UConn Huskies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eastRegionalChampion Context triple: [2014 NCAA Division I men's basketball tournament, eastRegionalChampion, UConn Huskies]
-
A.
conferenceChampionEastern
Indicates that the entity is the champion of the Eastern conference in a given competition or season.
-
B.
NLCentralChampion
Indicates that an entity has won the championship title in the National League Central division.
-
C.
zoneChampionship
Indicates that an entity has won or is associated with a championship title within a specific geographic or competitive zone.
-
D.
regionWinner
chosen
Indicates that an entity is the winner of a specified region in a competition, contest, or selection process.
-
E.
nationalLeagueEastChampion
Indicates that an entity is the team that won the National League East division championship in a given season.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f9887888190b67348ab0035412b |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.