Triple
T36598934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group B Streptococcus |
E902870
|
entity |
| Predicate | hemolysisType |
P185916
|
FINISHED |
| Object | beta-hemolytic |
—
|
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: beta-hemolytic | Statement: [Group B Streptococcus, hemolysisType, beta-hemolytic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hemolysisType Context triple: [Group B Streptococcus, hemolysisType, beta-hemolytic]
-
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.
bloodTrait
Indicates that one entity has a specific blood-related characteristic, property, or attribute associated with another entity.
-
C.
hasBloodPigment
Indicates that an organism possesses a specific pigment in its blood responsible for coloration and often for oxygen transport.
-
D.
bloodTypeCarried
Indicates that a particular blood type is transported, contained, or conveyed by a given carrier (such as a person, organ, or storage medium).
-
E.
hasBloodTypeSystem
Indicates that an entity uses or is classified according to a particular blood type classification system (e.g., ABO, Rh).
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.