Triple
T38455586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katharine Cushing |
E912305
|
entity |
| Predicate | familyNotabilityArea |
P193870
|
FINISHED |
| Object | medicine |
—
|
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: medicine | Statement: [Katharine Cushing, familyNotabilityArea, medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNotabilityArea Context triple: [Katharine Cushing, familyNotabilityArea, medicine]
-
A.
familyContext
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
-
B.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
C.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
D.
familyApplication
Indicates that an application or request is made in the context of a family relationship, typically involving or affecting multiple family members.
-
E.
familyIndicator
Indicates that there exists a familial relationship or family-based connection between the referenced entities.
- F. None of above. chosen
Provenance (4 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 3, 2026, 4:31 p.m.