Triple
T32116600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misbun Sidek |
E820253
|
entity |
| Predicate | activeAsCoachInPeriod |
P15414
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Misbun Sidek, activeAsCoachInPeriod, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsCoachInPeriod Context triple: [Misbun Sidek, activeAsCoachInPeriod, 1990s]
-
A.
isActiveAsCoach
Indicates that an entity is currently functioning in the role of a coach within a given context or organization.
-
B.
yearsActiveAsCoach
chosen
Indicates the span of time, typically in years, during which an individual has served in a coaching role.
-
C.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
D.
joinedTeamAsCoachYear
Indicates the year in which an individual joined a team specifically in the role of coach.
-
E.
hasCoachingExperienceAs
Indicates that an entity has experience providing coaching in a specified role or capacity.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 12:28 a.m.