Triple
T19641427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Australia Ministerial Consultations |
E471548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | annual ministerial meeting |
C14081
|
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: annual ministerial meeting Context triple: [United States–Australia Ministerial Consultations, instanceOf, annual ministerial meeting]
-
A.
yearly meeting
chosen
A yearly meeting is a scheduled gathering that occurs once every year for participants to review progress, make decisions, and plan future activities.
-
B.
annual international conference
An annual international conference is a recurring global event where experts, practitioners, and stakeholders from various regions gather once a year to share research, exchange ideas, and collaborate on topics within a specific field or industry.
-
C.
session of the United Nations General Assembly
A session of the United Nations General Assembly is a formally convened period during which all UN member states meet to discuss, debate, and make decisions on international issues through resolutions and other collective actions.
-
D.
United Nations General Assembly session
A United Nations General Assembly session is a formal gathering of all UN member states convened to debate, negotiate, and adopt resolutions on global issues within the Assembly’s mandate.
-
E.
biennial conference
A biennial conference is a large, organized gathering of participants held every two years to share knowledge, present research, and foster collaboration within a specific field or community.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:44 p.m.