Triple
T27781509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biodiversity Information Standards (TDWG) standards |
E699344
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biodiversity informatics standard |
C53335
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: biodiversity informatics standard Context triple: [Biodiversity Information Standards (TDWG) standards, instanceOf, biodiversity informatics standard]
-
A.
biodiversity database
A biodiversity database is a structured digital repository that stores, organizes, and provides access to data on species, their distributions, traits, and ecological relationships to support research, conservation, and environmental management.
-
B.
biodiversity assessment
Biodiversity assessment is the systematic evaluation and measurement of the variety, abundance, and distribution of species, genes, and ecosystems within a defined area to understand ecological health and inform conservation decisions.
-
C.
biodiversity indicator
A biodiversity indicator is a measurable attribute or index used to assess the state, trends, or changes in biological diversity within an ecosystem, region, or globally.
-
D.
biological database
A biological database is an organized, searchable repository that stores, manages, and provides access to biological information such as sequences, structures, functions, and interactions of biomolecules and organisms.
-
E.
zoological code
A zoological code is a formal system of rules and conventions that governs the scientific naming, classification, and nomenclatural validity of animal species.
- F. None of above. chosen
Provenance (1 batch)
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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 5:10 p.m.