Triple
T10958884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All England Open Badminton Championships |
E258913
|
entity |
| Predicate | initialEvents |
P96841
|
FINISHED |
| Object | men's doubles |
—
|
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: men's doubles | Statement: [All England Open Badminton Championships, initialEvents, men's doubles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialEvents Context triple: [All England Open Badminton Championships, initialEvents, men's doubles]
-
A.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
B.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
C.
initialAction
Indicates the first or starting action taken in a sequence of actions or events.
-
D.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
E.
introductionEvent
Indicates an event in which one entity is formally presented or made known to another entity or audience for the first time.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77127b10481908ad1efafb2a338d1 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.