Triple
T10219619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Sloan Sports Analytics Conference |
E242539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic-industry 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: academic-industry conference Context triple: [MIT Sloan Sports Analytics Conference, instanceOf, academic-industry 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.
academic exchange organization
An academic exchange organization is an institution that facilitates and manages educational and cultural exchange programs between students, scholars, or institutions across different regions or countries.
-
C.
academic association
An academic association is an organized group of scholars, researchers, and professionals dedicated to advancing knowledge, collaboration, and standards within a specific academic discipline or field.
-
D.
academic–industry collaboration scheme
An academic–industry collaboration scheme is a structured framework that facilitates joint research, knowledge transfer, and innovation between universities and commercial organizations through coordinated projects, funding mechanisms, and shared resources.
-
E.
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.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:08 a.m.