Triple
T7034411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region of Kainuu |
E163343
|
entity |
| Predicate | hasRegionalBird |
P297
|
FINISHED |
| Object | willow ptarmigan |
—
|
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: willow ptarmigan | Statement: [Region of Kainuu, hasRegionalBird, willow ptarmigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalBird Context triple: [Region of Kainuu, hasRegionalBird, willow ptarmigan]
-
A.
hasBirdSpecies
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
-
B.
stateBird
chosen
Indicates that a particular bird species is officially designated as the state bird of a given state or region.
-
C.
hasBirdColony
Indicates that one entity hosts or contains a colony of birds associated with it.
-
D.
hasMigratoryBirdUse
Indicates that an entity is used, visited, or relied upon by migratory birds, such as for feeding, resting, or breeding during migration.
-
E.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.