Triple
T8501704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthropocene Working Group |
E201232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subcommission working group |
C14322
|
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: subcommission working group Context triple: [Anthropocene Working Group, instanceOf, subcommission working group]
-
A.
subcommittee of a United Nations committee
A subcommittee of a United Nations committee is a smaller, specialized body established under a parent UN committee to focus on specific issues, conduct detailed analysis, and make recommendations to support the committee’s broader mandate.
-
B.
governing body subcommittee
chosen
A governing body subcommittee is a smaller, specialized group formed within a larger decision-making organization to focus on specific issues, conduct detailed analysis, and make recommendations or decisions within its defined scope.
-
C.
collaborative working group
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.
-
D.
ISO/IEC subcommittee
An ISO/IEC subcommittee is a specialized working group within the joint International Organization for Standardization and International Electrotechnical Commission structure that develops, maintains, and oversees standards in a specific technical or thematic area.
-
E.
subgroup
A subgroup is a subset of a group that is itself a group under the same binary operation, containing the identity, inverses, and being closed under the operation.
- 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.