Triple
T31694226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mountain forests |
E808875
|
entity |
| Predicate | commonInsectDisturbance |
P156729
|
FINISHED |
| Object | mountain pine beetle |
—
|
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: mountain pine beetle | Statement: [Rocky Mountain forests, commonInsectDisturbance, mountain pine beetle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInsectDisturbance Context triple: [Rocky Mountain forests, commonInsectDisturbance, mountain pine beetle]
-
A.
interactionWithInsects
Indicates a relationship where an entity engages in some form of contact, behavior, or exchange involving insects.
-
B.
insectGroup
Indicates that one or more insects belong to, or are classified within, a particular group or category of insects.
-
C.
pollinators
Indicates that one entity serves as an agent that transfers pollen to another entity, facilitating its reproduction.
-
D.
pestCommonName
chosen
Indicates the commonly used or vernacular name assigned to a pest in everyday language or practice.
-
E.
invertebrateFauna
Indicates that the subject has or is associated with a collection or community of animals lacking a vertebral column (invertebrates).
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 30, 2026, 11:09 p.m.