Triple
T10120297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All England Open Badminton Championships men's doubles |
E223268
|
entity |
| Predicate | drawFormat |
P130
|
FINISHED |
| Object | knockout |
—
|
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: knockout | Statement: [All England Open Badminton Championships men's doubles, drawFormat, knockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drawFormat Context triple: [All England Open Badminton Championships men's doubles, drawFormat, knockout]
-
A.
individualDrawFormat
Indicates the specific structure or format used to organize and schedule matches for individual competitors in a draw or bracket.
-
B.
draftFormatUsed
Indicates that a particular draft was created or prepared using a specified format.
-
C.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2659cdc8190b3ba91426bda55ec |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.