Triple
T8919160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rauschenberg Overseas Culture Interchange |
E212367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural exchange initiative |
C4457
|
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: cultural exchange initiative Context triple: [Rauschenberg Overseas Culture Interchange, instanceOf, cultural exchange initiative]
-
A.
cultural exchange network
chosen
A cultural exchange network is a structured system that connects individuals or groups from different cultural backgrounds to share traditions, knowledge, and experiences, fostering mutual understanding and collaboration.
-
B.
international initiative
An international initiative is a coordinated effort among multiple countries or global organizations aimed at addressing shared challenges or achieving common goals across national borders.
-
C.
educational exchange organization
An educational exchange organization facilitates cross-cultural learning experiences by coordinating programs that enable students, educators, and institutions from different countries to study, teach, and collaborate abroad.
-
D.
diplomatic initiative
A diplomatic initiative is a coordinated effort by one or more states or international actors to open, advance, or resolve political, economic, or security issues through negotiation and dialogue rather than coercion or conflict.
-
E.
cultural event
A cultural event is a planned gathering or activity that showcases, celebrates, or transmits the traditions, arts, values, or practices of a particular community or society.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.