Triple
T38455585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katharine Cushing |
E912305
|
entity |
| Predicate | notableFamilyContext |
P159380
|
FINISHED |
| Object | prominent American Cushing family |
—
|
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: prominent American Cushing family | Statement: [Katharine Cushing, notableFamilyContext, prominent American Cushing family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyContext Context triple: [Katharine Cushing, notableFamilyContext, prominent American Cushing family]
-
A.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
B.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
C.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
D.
familyNotableMember
chosen
Indicates that a particular individual is a distinguished or noteworthy member of a given family.
-
E.
notableLeaderFamily
Indicates that a person belongs to the family of a notable or prominent leader.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.