Triple
T692242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isoptera |
E13818
|
entity |
| Predicate | hasEcologicalImpact |
P8224
|
FINISHED |
| Object | nutrient cycling |
—
|
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: nutrient cycling | Statement: [Isoptera, hasEcologicalImpact, nutrient cycling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcologicalImpact Context triple: [Isoptera, hasEcologicalImpact, nutrient cycling]
-
A.
hasEnvironmentalImpactOn
Indicates that one entity affects or alters the environmental conditions, quality, or ecological state of another entity.
-
B.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
C.
environmentalSignificance
Indicates the importance or impact that something has on the natural environment, such as its role in conservation, degradation, or ecological balance.
-
D.
hasEcosystemService
chosen
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
-
E.
hasClimateInfluence
Indicates that one entity affects or contributes to the climate characteristics or climate-related conditions of another entity.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0b05f2c8190876c73db15b489a2 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.