Triple
T8501702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthropocene Working Group |
E201232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific working group |
C17702
|
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 working group Context triple: [Anthropocene Working Group, instanceOf, scientific working group]
-
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.
collaborative working group
chosen
A collaborative working group is a coordinated team of individuals who share responsibilities, knowledge, and decision-making to achieve a common goal or complete a specific project.
-
C.
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.
-
D.
division of a scientific society
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
-
E.
intergovernmental working group
An intergovernmental working group is a collaborative body composed of representatives from multiple governments tasked with developing, coordinating, or advising on policies, standards, or actions in a specific issue area.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:14 p.m.