Triple
T8400914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Relations Service |
E198167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mediation service |
C18889
|
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: mediation service Context triple: [Community Relations Service, instanceOf, mediation service]
-
A.
mediation support function
chosen
A mediation support function is a structured capability or service that provides tools, processes, and expertise to help design, facilitate, and manage mediation activities between disputing parties.
-
B.
labor mediator
A labor mediator is a neutral third party who facilitates communication and negotiation between employers and employees (or their representatives) to help resolve workplace or collective bargaining disputes without resorting to litigation or strikes.
-
C.
through service
A through service is a transportation offering in which a vehicle or passenger travels from origin to destination across one or more intermediate points without requiring a transfer or change of service.
-
D.
public service advocate
A public service advocate is an individual who actively promotes, defends, and advances the interests of the public by influencing policies, raising awareness, and ensuring government and institutions are accountable and responsive to community needs.
-
E.
cultural mediator
A cultural mediator is a person who facilitates understanding, communication, and collaboration between individuals or groups from different cultural backgrounds by interpreting, translating, and contextualizing their values, practices, and perspectives.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:04 p.m.