Triple
T23930978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big 12 Player of the Year |
E602493
|
entity |
| Predicate | firstWinnerSchool |
P127420
|
FINISHED |
| Object | Kansas Jayhawks |
—
|
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: Kansas Jayhawks | Statement: [Big 12 Player of the Year, firstWinnerSchool, Kansas Jayhawks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWinnerSchool Context triple: [Big 12 Player of the Year, firstWinnerSchool, Kansas Jayhawks]
-
A.
firstWinnerCollege
chosen
Indicates that the referenced college is the institution attended by the person or team that achieved first place in a given competition or event.
-
B.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
C.
firstWinnerTeam
Indicates that the referenced team is the one that secured first place or victory in a given competition or event.
-
D.
runnerUpSchool
Indicates that a school finished in second place (as the runner-up) in a specified competition or event.
-
E.
firstRunningWinner
Indicates that the subject is the first entity to win among those participating in a running event or race.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf9b4ae88190b3f4fee69d24bc33 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:57 p.m.