Triple
T1773248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angiosperm Phylogeny Group |
E38921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific collaboration |
C343
|
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: scientific collaboration Context triple: [Angiosperm Phylogeny Group, instanceOf, scientific collaboration]
-
A.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
-
B.
scientific endeavor
A scientific endeavor is a systematic, evidence-based pursuit aimed at discovering, explaining, and predicting natural or social phenomena through observation, experimentation, and critical analysis.
-
C.
scientific flourishing
Scientific flourishing is the sustained, collaborative advancement of rigorous inquiry, creativity, and ethical application of knowledge that expands understanding and benefits society.
-
D.
research support community
A research support community is a collaborative network of individuals and resources that provides guidance, feedback, tools, and encouragement to help researchers conduct, improve, and share their work.
-
E.
research consortium
chosen
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.