Triple
T22681963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian SuperLiga |
E560503
|
entity |
| Predicate | hasPlayoffsInSomeSeasons |
P2675
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Serbian SuperLiga, hasPlayoffsInSomeSeasons, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayoffsInSomeSeasons Context triple: [Serbian SuperLiga, hasPlayoffsInSomeSeasons, yes]
-
A.
hasPlayoffImplicationsInSomeYears
Indicates that the outcome of the related event or matchup affects playoff qualification or seeding in at least some seasons, but not necessarily every year.
-
B.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
C.
usesPlayoffs
chosen
Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
-
D.
reachedPlayoffs
Indicates that a team or competitor successfully qualified for and participated in the playoff stage of a competition.
-
E.
madePlayoffsInSeason
Indicates that a team qualified for and participated in the playoffs during a specified season.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786113a881908f60285054d7ecfb |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.