Triple
T35598002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Youth Congress of Esperanto |
E1028690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international Esperanto event |
C9539
|
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 Esperanto event Context triple: [International Youth Congress of Esperanto, instanceOf, international Esperanto event]
-
A.
Esperanto organization
An Esperanto organization is a group or institution dedicated to promoting, teaching, using, and supporting the international language Esperanto and its associated culture and ideals.
-
B.
international media event
An international media event is a globally significant occurrence or spectacle that attracts extensive, coordinated coverage across multiple countries and media platforms, shaping public attention and discourse worldwide.
-
C.
recurring international event
A recurring international event is a regularly scheduled gathering or activity that takes place across national boundaries, bringing together participants from multiple countries around a common purpose or theme.
-
D.
international youth meeting
chosen
An international youth meeting is a gathering where young people from different countries come together to exchange ideas, learn from each other, and collaborate on shared projects or issues.
-
E.
international auxiliary language project
An international auxiliary language project is an organized effort to design, develop, or promote a constructed language intended to facilitate communication between speakers of different native languages on a global scale.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.