Triple
T22674373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merger Working Group |
E560306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ICN 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: ICN working group Context triple: [Merger Working Group, instanceOf, ICN working group]
-
A.
IETF working group
An IETF working group is a collaborative, time-bounded team of experts chartered within the Internet Engineering Task Force to develop, discuss, and standardize specific Internet technologies or protocols.
-
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.
IRTF research group
An IRTF research group is a collaborative team within the Internet Research Task Force that investigates long-term, exploratory topics related to the evolution and future of Internet technologies.
-
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.
United States national committee of the IEC
The United States National Committee of the IEC is the U.S. body responsible for coordinating national participation in the International Electrotechnical Commission’s standardization activities and representing U.S. interests in global electrotechnical standards development.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:10 p.m.