Triple
T26989912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Society Public Engagement team |
E679837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public engagement team |
C18385
|
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: public engagement team Context triple: [Royal Society Public Engagement team, instanceOf, public engagement team]
-
A.
team
chosen
A team is a group of individuals who collaborate toward a shared goal, combining their skills, roles, and efforts to achieve outcomes they could not accomplish alone.
-
B.
public policy engagement
Public policy engagement is the process by which individuals, organizations, and communities actively participate in shaping, influencing, and implementing government policies through advocacy, consultation, collaboration, and public dialogue.
-
C.
rally team
A rally team is a coordinated group of drivers, co-drivers, engineers, and support staff who work together to prepare, operate, and manage a rally car in competitive rally events.
-
D.
community engagement initiative
A community engagement initiative is a coordinated effort designed to actively involve local stakeholders in collaborative activities, decision-making, and problem-solving to improve shared social, cultural, or environmental outcomes.
-
E.
collaborative working group
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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:51 a.m.