Triple
T12763933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legionella |
E305069
|
entity |
| Predicate | riskFactorEnvironment |
P66795
|
FINISHED |
| Object | stagnant water |
—
|
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: stagnant water | Statement: [Legionella, riskFactorEnvironment, stagnant water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskFactorEnvironment Context triple: [Legionella, riskFactorEnvironment, stagnant water]
-
A.
environmentalFactor
Indicates that one entity functions as an environmental influence or condition that affects another entity or process.
-
B.
hasEnvironmentalRisk
Indicates that an entity poses, contributes to, or is associated with potential harm or adverse impact on the environment.
-
C.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
D.
riskFactorForInfection
chosen
Indicates that something increases the likelihood or susceptibility of an entity to develop a particular infection.
-
E.
threatFactors
Indicates that certain conditions, elements, or circumstances contribute to increasing the risk or likelihood of a harmful or adverse outcome.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8f9f588190bffdea878856204b |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.