Triple
T37945776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terribacillus |
E946601
|
entity |
| Predicate | familyIncludesGenus |
P193585
|
FINISHED |
| Object | Bacillaceae |
—
|
NE NERFINISHED |
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: Bacillaceae | Statement: [Terribacillus, familyIncludesGenus, Bacillaceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyIncludesGenus Context triple: [Terribacillus, familyIncludesGenus, Bacillaceae]
-
A.
genusIncludes
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
-
B.
typeSpeciesOfFamily
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a particular family.
-
C.
animalGroupIncluded
Indicates that a particular animal is a member of, or belongs to, a specified animal group.
-
D.
speciesGrouping
Indicates a relationship where multiple organisms are classified or organized together based on shared species-level characteristics or taxonomic criteria.
-
E.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:20 p.m.