Triple
T28031924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knockouts World Championship |
E708294
|
entity |
| Predicate | scriptedSport |
P171447
|
FINISHED |
| Object | sports entertainment |
—
|
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: sports entertainment | Statement: [Knockouts World Championship, scriptedSport, sports entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptedSport Context triple: [Knockouts World Championship, scriptedSport, sports entertainment]
-
A.
sportsProgram
Indicates a relationship where an entity is a sports-related program, event, or broadcast organized or provided by another entity.
-
B.
streamsSport
Indicates that one entity broadcasts or provides live coverage of a particular sport.
-
C.
scripted
Indicates that one entity has written or created the script or dialogue for another entity or event.
-
D.
sportsAndEntertainmentChannel
Indicates a channel whose primary content focuses on sports events and entertainment programming.
-
E.
scriptedAs
Indicates that one entity is written or programmed to behave, appear, or function in the manner defined by another entity (such as a script, role, or specification).
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 8:17 p.m.