Triple
T35488708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB Goodwill Ambassador |
E1025668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community outreach role |
C56382
|
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: community outreach role Context triple: [MLB Goodwill Ambassador, instanceOf, community outreach role]
-
A.
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.
-
B.
community engagement campaign
A community engagement campaign is a coordinated set of activities and communications designed to inform, involve, and motivate community members to participate in achieving a shared goal or addressing a common issue.
-
C.
community development leader
chosen
A community development leader is an individual who mobilizes local stakeholders, resources, and partnerships to plan, implement, and sustain initiatives that improve the social, economic, and environmental well-being of a community.
-
D.
community organisation
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
E.
community event
A community event is a planned gathering or activity that brings members of a local group or neighborhood together for a shared purpose, such as celebration, education, support, or civic engagement.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.