Triple
T36170206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBMS-NSF Regional Conference Series in Applied Mathematics lectures |
E1046123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mathematics lecture series |
C12213
|
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: mathematics lecture series Context triple: [CBMS-NSF Regional Conference Series in Applied Mathematics lectures, instanceOf, mathematics lecture series]
-
A.
mathematics seminar
A mathematics seminar is a structured academic gathering where participants present, discuss, and critically examine mathematical research, problems, or theories.
-
B.
collection of lectures
chosen
A collection of lectures is an organized set of related instructional talks, typically grouped by subject or course, intended to convey knowledge in a structured sequence.
-
C.
public lecture
A public lecture is a structured, often one-off presentation delivered by an expert or knowledgeable speaker to a general audience, typically free or low-cost, with the aim of sharing information, insights, or ideas on a specific topic.
-
D.
collection of lecture notes
A collection of lecture notes is an organized set of written or digital materials that capture, summarize, and structure the content presented across multiple lectures on a particular subject or course.
-
E.
software engineering lecture series
A software engineering lecture series is a structured sequence of instructional sessions that systematically covers principles, methods, and tools for designing, developing, testing, and maintaining software systems.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.