Triple
T28870495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Strong |
E732127
|
entity |
| Predicate | conferenceChampionshipWonWith |
P177321
|
FINISHED |
| Object | Louisville Cardinals football |
—
|
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: Louisville Cardinals football | Statement: [Charlie Strong, conferenceChampionshipWonWith, Louisville Cardinals football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceChampionshipWonWith Context triple: [Charlie Strong, conferenceChampionshipWonWith, Louisville Cardinals football]
-
A.
conferenceChampionshipWonCount
Indicates the number of conference championships that have been won.
-
B.
teamWonChampionship
Indicates that a particular team has secured victory in a championship competition.
-
C.
wonChampionshipAsPlayerWith
Indicates that one entity won a championship while playing on a team or alongside the other entity.
-
D.
conferenceChampionshipAppearances
Indicates the number of times an entity has participated in a conference championship event or game.
-
E.
wonConferenceChampionshipsIn
Indicates that an entity has secured one or more conference championship titles in a specified league, sport, or time period.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 28, 2026, 7:32 a.m.