Triple
T31454362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudirman Cup |
E802409
|
entity |
| Predicate | eventIncludesDiscipline |
P137995
|
FINISHED |
| Object | men's singles |
—
|
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 singles | Statement: [Sudirman Cup, eventIncludesDiscipline, men's singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventIncludesDiscipline Context triple: [Sudirman Cup, eventIncludesDiscipline, men's singles]
-
A.
hasRacingDiscipline
Indicates that an entity participates in, is associated with, or is characterized by a specific type or category of racing discipline.
-
B.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
includesDisciplineCategory
chosen
Indicates that one entity encompasses or contains a specific discipline category as part of its overall scope or classification.
-
D.
hostedDiscipline
Indicates that an entity served as the host or venue for a particular discipline, event category, or field of competition.
-
E.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 9:15 p.m.