Triple
T9517049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yap Kim Hock |
E229550
|
entity |
| Predicate | hasPlayedEvent |
P22468
|
FINISHED |
| Object | Olympic badminton men's doubles |
—
|
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: Olympic badminton men's doubles | Statement: [Yap Kim Hock, hasPlayedEvent, Olympic badminton men's doubles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedEvent Context triple: [Yap Kim Hock, hasPlayedEvent, Olympic badminton men's doubles]
-
A.
wasPlayed
Indicates that an entity (such as a game, song, or media item) was performed, executed, or used by someone or something.
-
B.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
C.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
D.
hasCoveredEvent
Indicates that one entity has reported on, documented, or provided coverage of a particular event.
-
E.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd987eefec8190b0db1928776bf02b |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.