Triple
T166500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | URSI Radio Science Meeting (in conjunction with AP-S Symposium) |
E3026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international conference |
C140
|
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 conference Context triple: [URSI Radio Science Meeting (in conjunction with AP-S Symposium), instanceOf, international conference]
-
A.
academic conference
chosen
An academic conference is a formal gathering of scholars, researchers, and professionals who present, discuss, and critique original research and developments within a specific field or interdisciplinary area.
-
B.
diplomatic conference
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
C.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
D.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
E.
international economic organization
An international economic organization is an institution formed by multiple countries to coordinate and regulate economic policies, trade, finance, and development across national borders.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.