Triple
T18266964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAAI Spring Symposium Series |
E437507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | artificial intelligence event |
C1824
|
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: artificial intelligence event Context triple: [AAAI Spring Symposium Series, instanceOf, artificial intelligence event]
-
A.
event
chosen
An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
-
B.
artificial intelligence competition
An artificial intelligence competition is an organized event where participants develop and pit AI systems against each other to solve defined tasks or challenges under specified rules and evaluation criteria.
-
C.
artificial intelligence
Artificial intelligence is a field of computer science focused on creating systems that can perform tasks that typically require human intelligence, such as learning, reasoning, perception, and decision-making.
-
D.
neural networks conference
A neural networks conference is a professional gathering where researchers, practitioners, and industry experts present, discuss, and collaborate on the latest advances, applications, and theories in neural network and deep learning technologies.
-
E.
event management app
An event management app is a software application that helps users plan, organize, promote, and track events by managing tasks such as scheduling, registrations, ticketing, communication, and attendee engagement.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.