Triple
T25637224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USC Trojans athletics |
E642738
|
entity |
| Predicate | futureConferenceChangeEffectiveSeason |
P159166
|
FINISHED |
| Object | 2024–25 |
—
|
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: 2024–25 | Statement: [USC Trojans athletics, futureConferenceChangeEffectiveSeason, 2024–25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureConferenceChangeEffectiveSeason Context triple: [USC Trojans athletics, futureConferenceChangeEffectiveSeason, 2024–25]
-
A.
plannedKickoffSeason
Indicates the season during which an event, project, or activity is scheduled to begin or kick off.
-
B.
dstSeason
Indicates the specific season during which daylight saving time (DST) is in effect for a given context or location.
-
C.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
D.
expansionSeason
Indicates the season or time period during which an expansion (such as growth, enlargement, or extension of something) takes place.
-
E.
sportSeasonOf
Indicates that one entity is a sports season that belongs to, or is part of, the overall history or schedule of the specified sport.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 5:34 p.m.