Triple
T28818165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteobacteria |
E727687
|
entity |
| Predicate | includesEntericBacteria |
P199524
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Proteobacteria, includesEntericBacteria, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEntericBacteria Context triple: [Proteobacteria, includesEntericBacteria, yes]
-
A.
bacteriumIdentifiedIn
Indicates that a specific bacterium has been detected, recognized, or confirmed as present in a particular sample, environment, or host.
-
B.
includesPathogensOf
Indicates that one entity contains or encompasses the pathogens that are associated with or originate from another entity.
-
C.
includesNitrifyingBacteria
Indicates that the subject contains or incorporates nitrifying bacteria as part of its composition or system.
-
D.
hasRindMicroflora
Indicates that an entity possesses or is associated with microbial communities located on its rind or outer surface.
-
E.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
| PDg | Predicate description generation | batch_69ff409ee6ec819088b7c13fabed2ac2 |
completed | May 9, 2026, 2:11 p.m. |
Created at: April 28, 2026, 6:33 a.m.