Triple
T20810721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | He Bingjiao |
E512289
|
entity |
| Predicate | governingBodyId |
P141916
|
FINISHED |
| Object | BWF ID |
—
|
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: BWF ID | Statement: [He Bingjiao, governingBodyId, BWF ID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyId Context triple: [He Bingjiao, governingBodyId, BWF ID]
-
A.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
B.
governingBody2
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
C.
governingBodyInArea
Indicates that one entity serves as the official governing authority or administrative body responsible for overseeing and managing another entity within a specified area or jurisdiction.
-
D.
governingBodyOrSupport
Indicates that one entity serves as the governing authority for, or provides official support to, another entity.
-
E.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d27a4881908b34679385d8b94b |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:40 p.m.