Triple
T10802805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-12 Coach of the Year |
E254883
|
entity |
| Predicate | usesSeason |
P4415
|
FINISHED |
| Object | NCAA basketball season |
—
|
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: NCAA basketball season | Statement: [Pac-12 Coach of the Year, usesSeason, NCAA basketball season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSeason Context triple: [Pac-12 Coach of the Year, usesSeason, NCAA basketball season]
-
A.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
B.
usedInSeason
chosen
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
C.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
D.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
E.
basedOnSeason
Indicates that something is determined, influenced, or derived according to a particular season or time of year.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7336feff88190b638b7d62d34da0e |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.