Triple
T21726868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat Lions |
E536296
|
entity |
| Predicate | activeUntilSeason |
P98493
|
FINISHED |
| Object | 2017 Indian Premier League |
—
|
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: 2017 Indian Premier League | Statement: [Gujarat Lions, activeUntilSeason, 2017 Indian Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeUntilSeason Context triple: [Gujarat Lions, activeUntilSeason, 2017 Indian Premier League]
-
A.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
-
B.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
C.
seasonalValidity
Indicates that something is valid, applicable, or in effect only during a specific season or set of seasons.
-
D.
activeAt
chosen
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
E.
activatedAnnuallyUntil
Indicates that an action or state is activated once each year and continues to do so repeatedly up to, but not beyond, a specified end date.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.