Triple
T37634977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gardnerella |
E936462
|
entity |
| Predicate | roleInMicrobiome |
P3571
|
FINISHED |
| Object | opportunistic pathogen |
—
|
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: opportunistic pathogen | Statement: [Gardnerella, roleInMicrobiome, opportunistic pathogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMicrobiome Context triple: [Gardnerella, roleInMicrobiome, opportunistic pathogen]
-
A.
roleInMacrocosmica
Indicates that an entity has a specific role or function within a larger, overarching system or macro-level structure.
-
B.
roleInEcosystem
chosen
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
C.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
-
D.
roleInDiseaseCycle
Indicates the specific function or contribution an entity has within the progression, transmission, or maintenance of a disease over time.
-
E.
isMicroorganism
Indicates that an entity is a microscopic living organism, such as a bacterium, virus, fungus, or protozoan.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: May 3, 2026, 4:18 p.m.