Triple
T18924345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotary district |
E462937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of Rotary International |
C2248
|
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: administrative division of Rotary International Context triple: [Rotary district, instanceOf, administrative division of Rotary International]
-
A.
Rotary International program
A Rotary International program is an organized initiative or service project sponsored by Rotary clubs or districts that advances Rotary’s mission of promoting humanitarian service, ethical leadership, and international understanding.
-
B.
Rotary club
A Rotary club is a local chapter of an international service organization where business and professional leaders volunteer their time and resources to promote humanitarian efforts, community service, and global goodwill.
-
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.
ISAF regional command
ISAF regional command is a military organizational unit responsible for planning, coordinating, and overseeing International Security Assistance Force operations within a designated geographic region.
-
E.
regional division
chosen
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.