Triple
T31454515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Women's Team Championships |
E802412
|
entity |
| Predicate | governingBodyRenamedToBWF |
P196208
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [World Women's Team Championships, governingBodyRenamedToBWF, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyRenamedToBWF Context triple: [World Women's Team Championships, governingBodyRenamedToBWF, 2006]
-
A.
governingBodyRenamingYear
chosen
Indicates the year in which a governing body officially changed its name.
-
B.
governingBodyLaterKnownAs
Indicates that the governing body of an entity was later renamed or became known by a different official title.
-
C.
governingBodyAfter
Indicates that one governing body succeeds another as the official authority over the same entity or jurisdiction.
-
D.
governingBodyPreviouslyKnownAs
Indicates that the governing body currently associated with an entity was formerly known by a different name.
-
E.
governingBodyNameAtTime
Indicates the name of the governing body that held authority over an entity during a specified time period.
- 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_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: April 30, 2026, 9:15 p.m.