Triple
T30288716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communications Committee (Trinity College Dublin Students' Union) |
E770310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communications committee |
C55931
|
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: communications committee Context triple: [Communications Committee (Trinity College Dublin Students' Union), instanceOf, communications committee]
-
A.
communications unit
A communications unit is a modular component responsible for managing, formatting, and transmitting information between systems, devices, or subsystems using defined communication protocols.
-
B.
communications function
The communications function is responsible for managing and facilitating the effective exchange of information between an organization and its internal and external stakeholders through various channels and strategies.
-
C.
communications council
chosen
A communications council is a governing or advisory body that develops, coordinates, and oversees an organization’s communication strategies, policies, and messaging across internal and external channels.
-
D.
telecommunications committee
A telecommunications committee is a group responsible for overseeing, planning, and guiding policies, standards, and initiatives related to communication networks and technologies within an organization or governing body.
-
E.
communications agency
A communications agency is a professional service firm that develops and executes strategic messaging, branding, and media outreach to help organizations effectively engage and influence their target audiences.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:46 p.m.