Triple
T10958941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF World Championships |
E258914
|
entity |
| Predicate | mixedGenderEvent |
P7453
|
FINISHED |
| Object | mixed doubles discipline |
—
|
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: mixed doubles discipline | Statement: [IBF World Championships, mixedGenderEvent, mixed doubles discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mixedGenderEvent Context triple: [IBF World Championships, mixedGenderEvent, mixed doubles discipline]
-
A.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
B.
multiSport
Indicates that an entity participates in, is associated with, or is designed for more than one sport.
-
C.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
D.
sportGender
chosen
Indicates that a sport or sporting event is associated with a particular gender category (e.g., men's, women's, mixed).
-
E.
mixedAt
Indicates that one entity has been combined or blended together with another entity (or entities), typically to form a mixture at a specific time or place.
- 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_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. |
Created at: April 8, 2026, 9:23 p.m.