Triple
T37412501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium marinum |
E929610
|
entity |
| Predicate | RunyonGroup |
P188048
|
FINISHED |
| Object | Group I |
—
|
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: Group I | Statement: [Mycobacterium marinum, RunyonGroup, Group I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RunyonGroup Context triple: [Mycobacterium marinum, RunyonGroup, Group I]
-
A.
editorialGroup
Indicates that an entity is associated with or belongs to a specific editorial group responsible for content oversight or decision-making.
-
B.
majorSyndicationCompany
Indicates that a company serves as a primary or leading syndication entity responsible for distributing content (such as media or programming) to multiple outlets.
-
C.
LancefieldGroup
Indicates the specific Lancefield serological group classification to which a streptococcal organism belongs.
-
D.
PrintzHolding
Indicates that an entity has received or holds a Printz Award or Printz Honor recognition.
-
E.
BaltimoreGroup
Indicates a relationship in which an entity is a member of, associated with, or classified under the group or category referred to as "BaltimoreGroup."
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.