Triple
T15794295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow State University botanical facilities |
E382936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | botanical facility network |
C23703
|
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: botanical facility network Context triple: [Moscow State University botanical facilities, instanceOf, botanical facility network]
-
A.
botanical garden facility
chosen
A botanical garden facility is a managed space dedicated to the collection, cultivation, display, and conservation of diverse plant species for education, research, and public enjoyment.
-
B.
botanical area
A botanical area is a defined region of land or space characterized by specific plant communities, vegetation types, and ecological conditions that distinguish it from surrounding areas.
-
C.
botanical library
A botanical library is a specialized collection and information center that curates, preserves, and provides access to literature, records, and reference materials related to plants, botany, and plant sciences.
-
D.
botanical resource
A botanical resource is any plant-based material, information, or facility that can be used for scientific study, conservation, education, or practical applications such as medicine, agriculture, or industry.
-
E.
botanical test garden
A botanical test garden is a specialized outdoor space where plants are cultivated, observed, and experimentally evaluated under controlled or semi-controlled conditions to study their growth, performance, and suitability for various uses or environments.
- F. None of above.
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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.