Triple
T34209403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knack Roeselare |
E877610
|
entity |
| Predicate | postSeasonFormat |
P2137
|
FINISHED |
| Object | playoffs |
—
|
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: playoffs | Statement: [Knack Roeselare, postSeasonFormat, playoffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postSeasonFormat Context triple: [Knack Roeselare, postSeasonFormat, playoffs]
-
A.
postseasonSeriesFormat
Indicates the specific structure or rules (such as number of games or progression) used to organize a postseason series between competitors.
-
B.
postseasonType
chosen
Indicates the specific kind of postseason competition or phase associated with an event or team.
-
C.
postseasonFormatChange
Indicates that the structure, rules, or qualification criteria of a postseason competition have been altered from a previous format.
-
D.
postSeasonUse
Indicates that an entity is used or active during a post-season period following a regular season or main event.
-
E.
postseasonPeriod
Indicates that a time span occurs during the postseason phase of a sports or competitive season, after the regular season has concluded.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71054384481908897507876233248 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.