Triple
T14342403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICCPS |
E355635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyber-physical systems conference |
C12866
|
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: cyber-physical systems conference Context triple: [ICCPS, instanceOf, cyber-physical systems conference]
-
A.
computer systems conference
chosen
A computer systems conference is a professional gathering where researchers, practitioners, and industry experts present, discuss, and evaluate advances in the design, implementation, and evaluation of computer systems and related technologies.
-
B.
control theory conference
A control theory conference is a professional gathering where researchers, practitioners, and students present, discuss, and advance methods for analyzing and designing systems that regulate dynamic behavior.
-
C.
aerospace conference
An aerospace conference is a professional gathering where experts, researchers, and industry stakeholders share advancements, discuss challenges, and collaborate on topics related to aeronautics and space technology.
-
D.
theoretical computer science conference
A theoretical computer science conference is a formal academic gathering where researchers present, discuss, and critique new results and ideas in areas such as algorithms, complexity theory, cryptography, and formal methods.
-
E.
cybersecurity system
A cybersecurity system is an integrated set of tools, policies, and processes designed to protect digital assets, networks, and data from unauthorized access, attacks, and damage.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:14 a.m.