Triple
T37001419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 NCAA Men’s Final Four |
E915359
|
entity |
| Predicate | championshipMatchup |
P120086
|
FINISHED |
| Object | Connecticut vs. Kentucky |
—
|
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: Connecticut vs. Kentucky | Statement: [2014 NCAA Men’s Final Four, championshipMatchup, Connecticut vs. Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipMatchup Context triple: [2014 NCAA Men’s Final Four, championshipMatchup, Connecticut vs. Kentucky]
-
A.
conferenceOfChampion
Indicates a relationship where a conference or event is held to recognize, feature, or determine a champion.
-
B.
conferenceMatchup
Indicates a competitive pairing or scheduled contest between participants within the same conference or organized group.
-
C.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
-
D.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
E.
championshipContext
chosen
Indicates that the related entities are connected through the context of a championship event, competition, or title.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:14 p.m.