Triple
T12367696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scalable Adaptive Multicast Research Group |
E294914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multicast research group |
C28297
|
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: multicast research group Context triple: [Scalable Adaptive Multicast Research Group, instanceOf, multicast research group]
-
A.
multicast registration protocol
A multicast registration protocol is a network mechanism that allows hosts or routers to dynamically join, leave, and advertise membership in multicast groups so that multicast traffic is efficiently delivered only to interested receivers.
-
B.
IRTF research group
chosen
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.
-
C.
wireless research center
A wireless research center is an organization dedicated to advancing wireless communication technologies through research, development, testing, and collaboration with industry and academia.
-
D.
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.
-
E.
multidisciplinary research unit
A multidisciplinary research unit is an organized group that integrates expertise, methods, and perspectives from multiple academic or professional fields to collaboratively investigate complex problems and generate comprehensive insights.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:54 p.m.