Triple
T24735717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligue de soccer élite du Québec |
E618409
|
entity |
| Predicate | primarySeasonTiming |
P13215
|
FINISHED |
| Object | summer months |
—
|
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: summer months | Statement: [Ligue de soccer élite du Québec, primarySeasonTiming, summer months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySeasonTiming Context triple: [Ligue de soccer élite du Québec, primarySeasonTiming, summer months]
-
A.
typicalSeasonTiming
chosen
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
B.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
C.
trainingSeason
Indicates the specific season or time period during which training activities or programs take place.
-
D.
primarySeasonLocation
Indicates the main geographic location where an entity’s primary season, activity period, or operations take place.
-
E.
seasonStartPosition
Indicates the point in time or order at which a particular season begins within a sequence or schedule.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 4:03 a.m.