Triple
T7383795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane Catherine Venn |
E170328
|
entity |
| Predicate | notableFamilyFor |
P76687
|
FINISHED |
| Object | intellectual life |
—
|
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: intellectual life | Statement: [Jane Catherine Venn, notableFamilyFor, intellectual life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyFor Context triple: [Jane Catherine Venn, notableFamilyFor, intellectual life]
-
A.
notableHolderFamily
Indicates that a particular family is notably associated with holding, possessing, or being custodians of the referenced entity.
-
B.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
-
C.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
D.
motherNotableFor
Indicates that an individual’s mother is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1cb0b8881908132383c0efb0503 |
completed | March 27, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0ebf9c88190af5a4d87d3fd338a |
completed | March 27, 2026, 9:04 p.m. |
Created at: March 27, 2026, 3:08 p.m.