Triple
T14130568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christiaan Bezuidenhout |
E350152
|
entity |
| Predicate | healthChallenge |
P109970
|
FINISHED |
| Object | childhood stutter |
—
|
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: childhood stutter | Statement: [Christiaan Bezuidenhout, healthChallenge, childhood stutter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthChallenge Context triple: [Christiaan Bezuidenhout, healthChallenge, childhood stutter]
-
A.
hasHealthGoal
Indicates that an entity has a specific health-related objective or target it is aiming to achieve.
-
B.
activityChallenged
Indicates that one entity has questioned, disputed, or formally contested the validity, appropriateness, or outcome of an activity involving another entity.
-
C.
healthTheme
chosen
Indicates that the subject is associated with, focuses on, or is characterized by a particular health-related topic or theme.
-
D.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
E.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:47 p.m.