Triple
T36194360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale University Office of International Affairs |
E1047081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international affairs office |
C3799
|
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: international affairs office Context triple: [Yale University Office of International Affairs, instanceOf, international affairs office]
-
A.
international public office
An international public office is an organizational unit within an intergovernmental or supranational body that performs administrative, regulatory, or policy functions across national boundaries in the public interest.
-
B.
international affairs program
An international affairs program is an academic course of study that examines global politics, economics, law, and culture to prepare students for careers in diplomacy, policy analysis, and international organizations.
-
C.
foreign affairs office
A foreign affairs office is an organizational unit responsible for managing a government’s or institution’s interactions, negotiations, and relationships with foreign entities, including states, organizations, and individuals.
-
D.
international office
chosen
An international office is an organizational unit that manages and supports an institution’s global activities, partnerships, and services for international stakeholders.
-
E.
faculty of international relations
The faculty of international relations is an academic unit that educates and conducts research on global politics, diplomacy, international law, and cross-border economic and cultural interactions.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.