Triple
T21683949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASL 2017 season |
E535181
|
entity |
| Predicate | seasonStructureChange |
P2147
|
FINISHED |
| Object | no spring and fall split 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: no spring and fall split season | Statement: [NASL 2017 season, seasonStructureChange, no spring and fall split season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonStructureChange Context triple: [NASL 2017 season, seasonStructureChange, no spring and fall split season]
-
A.
seasonStructure
chosen
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
B.
tradeSeason
Indicates a specific period or season during which trading activities or exchanges are allowed, active, or most commonly occur.
-
C.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
D.
seasonAlignment
Indicates how the timing or characteristics of one entity’s season correspond, match, or are synchronized with those of another entity.
-
E.
seasonResumptionState
Indicates the current status or phase of a season’s restart or continuation after a pause or interruption.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c943888190acd783ce8677087c |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.