Triple
T29915245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore-Washington Conference of the United Methodist Church |
E759777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regional governing body |
C56524
|
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: Regional governing body Context triple: [Baltimore-Washington Conference of the United Methodist Church, instanceOf, Regional governing body]
-
A.
Regional At-Large Organization
A Regional At-Large Organization is a geographically defined body that represents and coordinates the interests, participation, and activities of individual Internet users and At-Large Structures within a specific region in global Internet governance processes.
-
B.
regional sports organization
A regional sports organization is an entity that governs, promotes, and coordinates athletic activities, competitions, and development programs within a specific geographic area.
-
C.
regional body of an international organization
A regional body of an international organization is a geographically focused subdivision that implements the organization’s policies, coordinates activities, and represents its interests within a specific region.
-
D.
continental sports governing body
A continental sports governing body is an organization that oversees, regulates, and promotes specific sports or groups of sports across countries within a particular continent.
-
E.
Sports federation umbrella organization
A sports federation umbrella organization is a governing body that coordinates, supports, and represents multiple sports federations or associations under a unified structure and policy framework.
- F. None of above. chosen
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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:12 p.m.