Triple
T27982444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada lynx |
E706657
|
entity |
| Predicate | rangeFluctuationCause |
P151508
|
FINISHED |
| Object | snowshoe hare population cycles |
—
|
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: snowshoe hare population cycles | Statement: [Canada lynx, rangeFluctuationCause, snowshoe hare population cycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeFluctuationCause Context triple: [Canada lynx, rangeFluctuationCause, snowshoe hare population cycles]
-
A.
edgeFluctuations
Indicates variations or instability occurring along the boundary or interface between two regions or elements.
-
B.
hasCauseOfVariability
chosen
Indicates a relationship where one factor or condition is identified as the source or driver of variation observed in another.
-
C.
flowVariation
Indicates how the rate or pattern of flow (such as water, traffic, or data) changes over time or across different conditions.
-
D.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
E.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b6a5fec81908e73597e2413bb1e |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:45 p.m.