Triple
T31141881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Team Speedway Championship |
E793807
|
entity |
| Predicate | hasSeasonOutcome |
P198438
|
FINISHED |
| Object | champion |
—
|
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: champion | Statement: [Polish Team Speedway Championship, hasSeasonOutcome, champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonOutcome Context triple: [Polish Team Speedway Championship, hasSeasonOutcome, champion]
-
A.
usesSeasonResults
Indicates that something bases its outcomes, decisions, or operations on the results from a particular season.
-
B.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
C.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
D.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
E.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
- F. None of above. chosen
Provenance (4 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
| PDg | Predicate description generation | batch_69fee33485188190a43526c9d39e3b6a |
completed | May 9, 2026, 7:33 a.m. |
Created at: April 29, 2026, 9:06 p.m.