Triple
T19870832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser Slave Lake Bird Observatory |
E477511
|
entity |
| Predicate | monitorsTaxon |
P99291
|
FINISHED |
| Object | migratory songbirds |
—
|
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: migratory songbirds | Statement: [Lesser Slave Lake Bird Observatory, monitorsTaxon, migratory songbirds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsTaxon Context triple: [Lesser Slave Lake Bird Observatory, monitorsTaxon, migratory songbirds]
-
A.
concernsTaxon
Indicates that something (such as a statement, record, or resource) is about, refers to, or is specifically related to a particular taxon.
-
B.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
C.
worksOnTaxa
chosen
Indicates that an agent is engaged in research, study, or other work involving specific taxa or taxonomic groups.
-
D.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
E.
characteristicTaxon
Indicates that one taxon is characteristic or typical of another taxonomic group, such as serving as a defining or representative member.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a3d2b08190ad81914d4860df0e |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.