Triple
T36846271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Kolisi |
E910555
|
entity |
| Predicate | roleAtKolisiFoundation |
P69206
|
FINISHED |
| Object | co-founder |
—
|
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: co-founder | Statement: [Rachel Kolisi, roleAtKolisiFoundation, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtKolisiFoundation Context triple: [Rachel Kolisi, roleAtKolisiFoundation, co-founder]
-
A.
roleInKuomboka
Indicates that an entity holds a specific role or function within the context of the Kuomboka ceremony or event.
-
B.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
C.
hasCoFounderRoleOf
chosen
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
D.
roleAtSKIMS
Indicates that an entity holds or held a specific role or position at the institution SKIMS.
-
E.
labelFounderCollaborator
Indicates that an entity is recognized as a collaborator who worked together with the founder in establishing or developing another entity.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.