Triple
T18531420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SymfonyLive |
E452838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | developer conference series |
C8849
|
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: developer conference series Context triple: [SymfonyLive, instanceOf, developer conference series]
-
A.
technology conference
chosen
A technology conference is a structured event where professionals, enthusiasts, and organizations gather to share knowledge, showcase innovations, and discuss trends and developments in technology.
-
B.
Konferenz
Eine Konferenz ist eine organisierte, meist zeitlich begrenzte Veranstaltung, bei der mehrere Personen zusammenkommen, um Informationen zu einem bestimmten Thema auszutauschen, zu präsentieren und zu diskutieren.
-
C.
series of international conferences
A series of international conferences is a recurring, organized set of global meetings held across different locations and times, bringing together participants from multiple countries to share knowledge, collaborate, and advance a specific field or theme.
-
D.
academic conference
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.
-
E.
education convention
An education convention is a large organized gathering where educators, administrators, students, and industry professionals meet to share knowledge, showcase innovations, and discuss trends and issues in teaching and learning.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.