Triple
T15010593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrietta Lacks |
E377824
|
entity |
| Predicate | cellsTakenWithConsent |
P116344
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Henrietta Lacks, cellsTakenWithConsent, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellsTakenWithConsent Context triple: [Henrietta Lacks, cellsTakenWithConsent, no]
-
A.
consentType
Indicates the specific kind or category of consent that has been given, requested, or recorded in the relationship.
-
B.
requiresConsentOfParties
Indicates that an action or agreement can only proceed if all involved parties have explicitly given their consent.
-
C.
consentTypeRequired
Indicates that a specific type or category of consent is required for the associated action or relationship to proceed.
-
D.
legalStatusAfterAssent
Indicates the legal status that an entity attains once formal assent or approval has been granted.
-
E.
canEnterIntoAgreementsWith
Indicates that one entity has the legal or formal capacity to make binding agreements or contracts with another entity.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded734943481908dad4ceed4fe850c |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.