Triple
T32497400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Committee |
E830564
|
entity |
| Predicate | worksOnSpeciesCategory |
P99291
|
FINISHED |
| Object | highly migratory species |
—
|
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: highly migratory species | Statement: [Northern Committee, worksOnSpeciesCategory, highly migratory species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnSpeciesCategory Context triple: [Northern Committee, worksOnSpeciesCategory, highly migratory species]
-
A.
worksOnTaxa
chosen
Indicates that an agent is engaged in research, study, or other work involving specific taxa or taxonomic groups.
-
B.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
C.
worksOnFeature
Indicates that an entity is actively involved in developing, implementing, or contributing to a particular feature.
-
D.
supportsSpeciesGroup
Indicates that one entity provides suitable conditions or resources that enable the survival or persistence of a particular group of species.
-
E.
belongsToSpecies
Indicates that an individual organism is a member of, or classified under, a particular biological species.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 12:59 a.m.