Triple
T16789125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nematomorpha |
E408056
|
entity |
| Predicate | hostImpact |
P124636
|
FINISHED |
| Object | usually non-lethal until emergence |
—
|
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: usually non-lethal until emergence | Statement: [Nematomorpha, hostImpact, usually non-lethal until emergence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostImpact Context triple: [Nematomorpha, hostImpact, usually non-lethal until emergence]
-
A.
impactOnOwner
Indicates that one entity has an effect, influence, or consequence on the owner entity.
-
B.
hasImpactScale
Indicates the degree or magnitude of impact that one entity or action has on another, typically expressed along a defined scale.
-
C.
homeFrontImpact
Indicates the effect that an event or action has on conditions, experiences, or activities in the domestic or civilian sphere away from the primary site of conflict or action.
-
D.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
-
E.
impactOnHumans
Indicates a relationship where something produces an effect, influence, or consequence on humans.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a50e18819090a30e1f38e520e0 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.