Triple
T32934549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goh Liu Ying |
E842490
|
entity |
| Predicate | hasBwfId |
P142292
|
FINISHED |
| Object | known professional BWF player ID (not specified here) |
—
|
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: known professional BWF player ID (not specified here) | Statement: [Goh Liu Ying, hasBwfId, known professional BWF player ID (not specified here)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBwfId Context triple: [Goh Liu Ying, hasBwfId, known professional BWF player ID (not specified here)]
-
A.
hasBNFId
Indicates that an entity is associated with a specific identifier from the British National Formulary (BNF) system.
-
B.
BWF_ID
chosen
Indicates the unique identifier assigned to an entity by the Badminton World Federation (BWF).
-
C.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
D.
hasBridgeID
Indicates that a bridge is associated with a specific identifying code or number.
-
E.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d108f2008190be705c3372b95fe5 |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.