Triple
T9634164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Hockey America |
E232885
|
entity |
| Predicate | tournamentWinnerReceives |
P14849
|
FINISHED |
| Object | automatic NCAA tournament bid |
—
|
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: automatic NCAA tournament bid | Statement: [College Hockey America, tournamentWinnerReceives, automatic NCAA tournament bid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentWinnerReceives Context triple: [College Hockey America, tournamentWinnerReceives, automatic NCAA tournament bid]
-
A.
winnerReceives
chosen
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
B.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
C.
tournamentsAward
Indicates that a tournament grants or confers a specific award or prize to an entity.
-
D.
winnerMake
Indicates that one entity causes or brings about another entity becoming the winner in a contest, competition, or selection process.
-
E.
winnerType
Indicates the category or kind of winner associated with an event, competition, or outcome.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2a0e2c8190ab5aaa223b1e1cde |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.