Triple
T27544311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WE League |
E695319
|
entity |
| Predicate | firstSeasonStart |
P53554
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [WE League, firstSeasonStart, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonStart Context triple: [WE League, firstSeasonStart, 2021]
-
A.
firstSeasonEndYear
Indicates the calendar year in which an entity’s first season or initial seasonal run concluded.
-
B.
firstSeasonReleaseYear
Indicates the calendar year in which the first season of something (such as a series or competition) was initially released or premiered.
-
C.
originalSeasonStart
chosen
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
D.
firstSeasonOf
Indicates that one entity is the first season installment belonging to the series or show represented by the other entity.
-
E.
firstSeasonScheduled
Indicates that the initial season of an entity (such as a show, competition, or event series) has been planned and assigned a 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: April 27, 2026, 1:32 p.m.