Triple
T3061087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFIP Working Group 2.1 |
E61997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IFIP technical committee working group |
C6251
|
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: IFIP technical committee working group Context triple: [IFIP Working Group 2.1, instanceOf, IFIP technical committee 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.
committee of the Association for Computing Machinery
A committee of the Association for Computing Machinery is a formally organized group of ACM members tasked with overseeing and advancing specific activities, policies, or areas of interest within the computing community.
-
C.
IETF area
An IETF area is a high-level organizational division within the Internet Engineering Task Force that groups related working groups and activities under a common technical or functional theme.
-
D.
international expert committee
chosen
An international expert committee is a formally organized group of specialists from multiple countries who collaboratively provide authoritative analysis, guidance, and recommendations on complex global issues within a specific domain.
-
E.
intergovernmental working group framework
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:02 p.m.