Triple
T5559645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monogenea |
E145732
|
entity |
| Predicate | impactOnHost |
P40373
|
FINISHED |
| Object | gill damage |
—
|
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: gill damage | Statement: [Monogenea, impactOnHost, gill damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnHost Context triple: [Monogenea, impactOnHost, gill damage]
-
A.
impactOnPerformance
Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
-
B.
effectOnSystem
chosen
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
C.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
D.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
E.
integrityImpact
Indicates the extent to which the relationship or action compromises, alters, or destroys the accuracy, consistency, or trustworthiness of the affected entity’s information or state.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020167afc8190b0c518907cd0d99b |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.