Triple
T10946389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFIP Working Group 2.3 |
E258607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IFIP 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: IFIP working group Context triple: [IFIP Working Group 2.3, instanceOf, IFIP 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.
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.
-
D.
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.
-
E.
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.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:23 p.m.