Triple
T4446013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes Valley Conference |
E96286
|
entity |
| Predicate | hasCompetitionSeason |
P26586
|
FINISHED |
| Object | fall |
—
|
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: fall | Statement: [Great Lakes Valley Conference, hasCompetitionSeason, fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionSeason Context triple: [Great Lakes Valley Conference, hasCompetitionSeason, fall]
-
A.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
B.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
C.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
D.
hasSeasonType
chosen
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
seasonOfCompetitionWon
Indicates the specific season of a competition in which an entity achieved a victory or championship.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d1eba08190899d0a3c1684ce4e |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.