Triple
T27295894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome Eugene Morrow |
E688762
|
entity |
| Predicate | bloodTypeInStory |
P143403
|
FINISHED |
| Object | valid genotype |
—
|
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: valid genotype | Statement: [Jerome Eugene Morrow, bloodTypeInStory, valid genotype]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodTypeInStory Context triple: [Jerome Eugene Morrow, bloodTypeInStory, valid genotype]
-
A.
bloodType
Indicates that one entity has a specific blood group classification (such as A, B, AB, or O, with a positive or negative Rh factor).
-
B.
bloodTypeRole
Indicates that an entity participates in a relationship specifically in the capacity of having or providing a particular blood type.
-
C.
bloodTypeCarried
Indicates that a particular blood type is transported, contained, or conveyed by a given carrier (such as a person, organ, or storage medium).
-
D.
bloodTrait
chosen
Indicates that one entity has a specific blood-related characteristic, property, or attribute associated with another entity.
-
E.
hasBlood
Indicates that one entity possesses or contains the blood of 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6277ff9848190958c203e511b1393 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:18 a.m.