Triple
T31119230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brevoortia |
E793177
|
entity |
| Predicate | impactOnWaterQuality |
P77889
|
FINISHED |
| Object | can influence plankton abundance |
—
|
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: can influence plankton abundance | Statement: [Brevoortia, impactOnWaterQuality, can influence plankton abundance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnWaterQuality Context triple: [Brevoortia, impactOnWaterQuality, can influence plankton abundance]
-
A.
waterQualityProtection
Indicates efforts, measures, or responsibilities aimed at preserving or improving the cleanliness, safety, and ecological integrity of water resources.
-
B.
hasWaterQualityImportance
chosen
Indicates that something plays a significant role in determining, influencing, or assessing the quality of water.
-
C.
waterQualityIssues
Indicates that there are problems or concerns with the condition, safety, or suitability of a water source.
-
D.
affectsWaterBody
Indicates that one entity has an impact on the condition, quality, or state of a water body.
-
E.
waterQualityUse
Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 9:04 p.m.