Triple
T16615593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Independent Science Board |
E403688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific advisory board |
C655
|
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 advisory board Context triple: [Delta Independent Science Board, instanceOf, scientific advisory board]
-
A.
scientific committee
A scientific committee is a group of experts who collaboratively evaluate, guide, and make decisions on scientific matters, such as research quality, funding, ethics, and strategic priorities.
-
B.
scientific collaboration board
A scientific collaboration board is a shared digital or physical workspace where researchers coordinate projects, exchange data and ideas, track progress, and manage collaborative tasks across institutions and disciplines.
-
C.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
D.
science policy coordination body
A science policy coordination body is an organization that aligns scientific research, evidence, and expertise with policymaking processes across institutions and sectors to ensure coherent, informed, and effective public policy.
-
E.
astronomical advisory committee
An astronomical advisory committee is a group of experts convened to provide informed guidance, recommendations, and oversight on policies, priorities, and strategies related to astronomical research and space science activities.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.